HaloPSA MCP — Claude Code MCP server: what it does, how to install
Connects HaloPSA, HaloITSM, and HaloCRM to your AI agent for ticket triage, SLA monitoring, and cross-client analytics via local SQLite.
Open on GitHubWhat HaloPSA MCP does
The server links your coding agent to HaloPSA APIs to handle incoming ticket routing, catch looming SLA breaches, and generate cross-client reporting. Instead of hammering the cloud endpoints directly, it maintains a local SQLite mirror. This lets your assistant query multi-tenant data for review meetings without hitting API rate limits.
Under the hood, the integration pairs the halopsa-mcp binary with the companion halopsa-cli tool. You must authenticate first by running halopsa-cli auth login using API credentials generated inside your tenant's integration settings.
Running with --transport http is insecure in this build because it lacks authentication and listens on all network interfaces. Stick strictly to the default stdio transport to prevent unwanted access through browser-rebinding attacks.
What it helps with
- triage incoming tickets across HaloPSA queues
- catch approaching SLA breaches before deadlines fail
- compile cross-client metrics for quarterly reviews
- query service desk history without exhausting API rate limits
Example prompts for the agent
- Check open tickets in HaloPSA and list any close to an SLA breach
- Generate a summary of ticket volume by client for last quarter's QBR
- Look up recent support requests for this client in the local SQLite mirror
How to install HaloPSA MCP
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about HaloPSA MCP
How do I install HaloPSA MCP in Claude Code?
Run /plugin marketplace add Servosity/msp-skills in your workspace, followed by /plugin install halopsa@msp-skills to complete the setup.
What is the purpose of the local SQLite mirror?
The local copy stores ticket and client records so your agent can execute cross-tenant analytics locally. This avoids cloud rate limits when compiling extensive reports.
Why is HTTP transport mode restricted?
The HTTP transport currently lacks password authentication and binds to all interfaces, exposing credentials to browser-rebinding exploits. Always use the standard stdio transport instead.
