HaloPSA ticket triage, SLA-breach pre-emption, and cross-client analytics for any MCP agent.
HaloPSA MCP is an MCP integration. HaloPSA ticket triage, SLA-breach pre-emption, and cross-client analytics for any MCP agent.
The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/halopsa-v0.2.18/halopsa-mcp.mcpb, version 0.2.18. Its declared MCP transport is stdio.
The package declares HALOPSA_BASE_URL: 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 (required): OAuth2 client_credentials ID from Configuration → Integrations → Halo PSA API.; HALOPSA_CLIENT_SECRET (required): OAuth2 client_credentials secret.; HALOPSA_DOMAIN: Domain template variable. Defaults to halopsa.com.; HALOPSA_OAUTH_SCOPE (required): Sets HALOPSA_OAUTH_SCOPE for the HaloPSA MCP server. Required by the generated client for credential refresh or hand-written auth flow.; HALOPSA_SCOPE: Optional. OAuth2 scope (defaults to "all"); set to a narrower scope when your API application requires it; HALOPSA_TENANT (required): Your HaloPSA tenant identifier.; HALOPSA_TOKEN: Optional. Pre-issued Bearer access token. Overrides the client_credentials flow when set.; HALOPSA_TOKEN_URL: Token endpoint the client-credentials exchange posts to. Leave blank: the CLI derives it from the base URL.; HALOPSA_NO_CONFIG_WRITE: 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..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.2.18 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| HALOPSA_BASE_URL | 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. | Optional |
| HALOPSA_CLIENT_ID | OAuth2 client_credentials ID from Configuration → Integrations → Halo PSA API. | Yes |
| HALOPSA_CLIENT_SECRET | OAuth2 client_credentials secret. | Yes |
| HALOPSA_DOMAIN | Domain template variable. Defaults to halopsa.com. | Optional |
| HALOPSA_OAUTH_SCOPE | Sets HALOPSA_OAUTH_SCOPE for the HaloPSA MCP server. Required by the generated client for credential refresh or hand-written auth flow. | Yes |
| HALOPSA_SCOPE | Optional. OAuth2 scope (defaults to "all"); set to a narrower scope when your API application requires it | Optional |
| HALOPSA_TENANT | Your HaloPSA tenant identifier. | Yes |
| HALOPSA_TOKEN | Optional. Pre-issued Bearer access token. Overrides the client_credentials flow when set. | Optional |
| HALOPSA_TOKEN_URL | Token endpoint the client-credentials exchange posts to. Leave blank: the CLI derives it from the base URL. | Optional |
| HALOPSA_NO_CONFIG_WRITE | 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. | Optional |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.