HaloPSA MCP
io.github.Servosity/halopsa-mcp
About HaloPSA MCP
HaloPSA MCP is an MCP server published by the GitHub account Servosity. HaloPSA ticket triage, SLA-breach pre-emption, and cross-client analytics for any MCP agent.
It runs on your own machine: your AI client starts it from the MCP bundle package halopsa-mcp.mcpb at version 0.2.22.
It asks for 4 secrets: HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_OAUTH_SCOPE and HALOPSA_TOKEN. Give it a key with the least access that still works.
It also needs HALOPSA_TENANT set before it starts.
Version 0.2.22 was published on 23 October 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 7 automated checks on registry metadata: 4 pass, 1 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
HALOPSA_BASE_URL | No | No | Full API base URL. Leave blank: the CLI builds it from HALOPSA_TENANT and HALOPSA_DOMAIN. Set it only to point at a different host. |
HALOPSA_CLIENT_ID | Yes | Yes | OAuth2 client_credentials ID from Configuration → Integrations → Halo PSA API. |
HALOPSA_CLIENT_SECRET | Yes | Yes | OAuth2 client_credentials secret. |
HALOPSA_DOMAIN | No | No | Domain template variable. Defaults to halopsa.com. |
HALOPSA_OAUTH_SCOPE | Yes | Yes | Sets HALOPSA_OAUTH_SCOPE for the HaloPSA MCP server. Required by the generated client for credential refresh or hand-written auth flow. |
HALOPSA_SCOPE | No | No | Optional. OAuth2 scope (defaults to "all"); set to a narrower scope when your API application requires it |
HALOPSA_TENANT | Yes | No | Your HaloPSA tenant identifier. |
HALOPSA_TOKEN | No | Yes | Optional. Pre-issued Bearer access token. Overrides the client_credentials flow when set. |
HALOPSA_TOKEN_URL | No | No | Token endpoint the client-credentials exchange posts to. Leave blank: the CLI derives it from the base URL. |
HALOPSA_NO_CONFIG_WRITE | No | No | Set to 1 to keep credentials off disk. The token cache becomes a no-op, so the connector mints a fresh token each run instead of writing one to config.toml. Leave blank for the default cached behaviour. |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/servosity/msp-skills |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Warn | Asks for 4 secrets: HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_OAUTH_SCOPE, HALOPSA_TOKEN |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account Servosity |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Code red flags | Info | Package could not be read (too large) |
Popularity & health: 63 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
14 forks, 379 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.Servosity/halopsa-mcp |
|---|---|
| Publisher | GitHub account Servosity |
| How the name is verified | Name verified via GitHub account Servosity. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | mcpb https://github.com/Servosity/msp-skills/releases/download/halopsa-v0.2.22/halopsa-mcp.mcpb 0.2.22 (stdio) |
| Version | 0.2.22 |
| Published | |
| Last updated | |
| Source repository | https://github.com/servosity/msp-skills |
| Website | None linked |
| Category | Analytics & monitoring (assigned by keyword rule, not by hand) |
Related servers in Analytics & monitoring
- Hive Sla Monitor3/3Service level agreement monitoring for the Hive agent fleet
- devicecloud7/7Triage failing DeviceCloud Maestro test runs: fail reasons,…
- SocialHive4/4Social media management, multi-platform publishing, AI generation,…
- unifi7/8UniFi semantic-analysis MCP — fleet health, anomaly detection,…
- Mammoth Analytics3/3Explore, clean, transform and export your Mammoth Analytics data…
- KadiConnect8/8Create a digital business card, tracked links and analytics from…