HaloPSA MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
HaloPSA MCP Server
A Model Context Protocol server that lets AI agents on the MSPbots Agent Platform work in HaloPSA: tickets and ticket notes, clients, sites, contacts, assets, agents and teams, invoices, and the reference tables (statuses, priorities, ticket types, categories) needed to write tickets correctly.
It runs as a stateless HTTP service behind the MSPbots MCP gateway. The gateway sends each tenant's HaloPSA credentials as request headers on every call; the server keeps nothing between requests.
MSPbots Connector
The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.
Get started at connect.mspbots.ai →
MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.
Hosted service: connect.mspbots.ai · Free to use.
Why Connector

Visible | Every tool call is logged: who, which vendor, when. Usage dashboard, CSV export, SIEM streaming. |
Controlled | Role-based, per-tool allowlist. Deny by default. |
Protected | Credentials encrypted per record. AI clients never see your vendor passwords or tokens. |
MSP-native | Built for the MSP stack only: RMM, PSA, documentation, security, finance. |
Quick start
Sign up at connect.mspbots.ai.
Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.
Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.
Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.
Ask your AI to do real work, and watch every call appear in the audit log.
Features
Unified gateway
One MCP URL for all your AI clients
150+ connectors across the MSP stack
Custom MCP servers supported, free
Authorization happens on each vendor's own page; the AI never sees passwords or tokens
Bring your own credentials: use the vendor API keys you already have
Multiple accounts per app; connect once, reuse across AI clients
Tool search: finds the right action for the task
One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically
Visibility
Audit log for every tool call (who, which vendor, when)
Usage dashboard: call volume, top vendors, error rate, per-user activity
Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)
Optional recording of tool arguments and result summaries (off by default, enabled per organization)
Control
Per-role, per-tool allowlist, deny by default
owner / admin / member roles
SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace
Security
Credentials encrypted one record at a time (AES-256-GCM, per-record key)
AI clients authenticate with OAuth 2.1 + PKCE
Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.
Static egress IP for customer firewall and API allowlisting
Pricing
Free.
Links: connect.mspbots.ai · mspbots.ai
Related MCP server: HaloPSA API Gateway MCP Server
Credentials (request headers)
Header | Required | Meaning |
| Yes | Client ID of a HaloPSA API application (Config > Integrations > Halo API > View Applications) using the Client ID and Secret (Services) authentication method. |
| Yes | Client secret of that application. |
| One of these two | Tenant name of a hosted instance: |
| One of these two | Instance URL, e.g. |
Header names are case-insensitive. A request to /mcp without the client ID, the secret, or both
the tenant and base URL gets 401 with the list of expected headers. The middleware only checks
that the headers are present; a malformed tenant or base URL is reported by each tool as
not_configured.
The server gets an OAuth2 token (client_credentials, scope=all) from <instance>/auth/token
on every tool call and calls the REST API at <instance>/api. When both a base URL and a tenant are
sent, the tenant is added to the token request as ?tenant= (as HaloPSA requires for some hosted
instances). Tokens are never cached between requests. Give the API application an agent with the
permissions the agents need (read tickets, clients, assets, invoices; write tickets, actions,
attachments, clients and contacts).
Tools
Area | Tools |
Discovery |
|
Tickets |
|
Clients |
|
Assets |
|
Agents and teams |
|
Invoices |
|
Reference data |
|
Contacts |
|
Sites |
|
Tool names and parameters match the previous HaloPSA connector on the MSPbots Agent Platform, so existing agents keep working. This is why the server has more than 20 tools.
Behaviour notes:
Every tool returns a JSON string. Errors use one envelope:
{"error": {"code": "...", "message": "...", "retryable": false}}withcodeone ofnot_configured,unauthorized,not_found,invalid_argument,rate_limited,upstream_error. HaloPSA's own error text is included in the message.List and search tools return
{"items", "count", "limit", "offset", "has_more"}(plustotal_countwhere HaloPSA reports it) and takeoffset. Whenhas_moreis true,next_offsetis where to continue; it always starts right after the last record returned, also when a page was cut to fit the 20,000-character limit (truncated). A call can return fewer thanlimitrecords while more remain.limitdefaults to 50 (25 for the search tools, 100 for asset types) and is capped at 200; tickets are capped at 100 per page (HaloPSA's maximum).page_noonhalopsa_tickets_liststill works. Records too long on their own come back with long fields shortened (fields_truncated), never as a text preview.All tools are always listed.
halopsa_navigateonly describes the tools of one area (teams are underagents);halopsa_statusshows which headers were sent, the instance URL and whether a token could be obtained, without revealing secrets.Tickets: a HaloPSA ticket has about 1,000 fields plus the full definition of every custom field (about 70,000 characters for a new ticket).
halopsa_tickets_get/create/updatereturn the fields agents use (summary, details, status, type, priority, client, site, contact, agent, team, categories, dates), related records reduced to{id, name}and only the custom fields that hold a value, unlessfull_responseis true. Withinclude_actions, actions are paged withactions_limit/actions_offset(next_actions_offset).halopsa_users_getreturns the contact the same way; the other get tools drop empty values and "no date" dates.halopsa_tickets_list_actionslists a ticket's actions with HaloPSA's own/Actionsfilters (exclude system events, exclude private notes, agent/supplier/important/child-notes-only, include HTML note/email body, include attachment info, SLA-only, conversation-only) passed through only when set. It returns a richer field set thaninclude_actionsabove (alsowho_type,who_agentid,note_html,old_status,attachment_count,replied_to_action_id) in the standard list envelope (items/offset/has_more/next_offset), and fails withnot_foundif the ticket does not exist rather than returning an empty list.halopsa_clients_create: HaloPSA has no phone or email on a client.phonenumberis saved on the main site andemailon the client's main contact (contact_name, default "Main Contact"; HaloPSA creates it with the client, otherwise it is added as a contact of the main site; no welcome email is sent); the result showsmain_phonenumber/main_contact_emailas HaloPSA stored them, with awarningif a value was not saved.Writes to a record that does not exist return
not_foundnaming it; invalid arguments (wrong type, missing, unknown value) return theinvalid_argumentenvelope.halopsa_tickets_updatechanges only the fields given.team_idassigns the team (the team name is looked up and sent with it);custom_fieldswrites custom fields by id or name;tickettype_idis applied through a hidden action and the ticket is re-read to confirm the change stuck, otherwise the tool returns an error.halopsa_tickets_add_actiontakes time spent in minutes, astime_taken_minutesortimetaken(the same thing; passing both isinvalid_argument), and sends HaloPSA decimal hours rounded to 4 places (11 minutes -> 0.1833). Returned actions keep HaloPSA'stimetakenin hours and addtime_taken_minutes.halopsa_tickets_add_attachmentuploads one file to a ticket withPOST /Attachment(data_base64, sent as the data URLdata:<type>;base64,...HaloPSA requires).contentis base64 (adata:<type>;base64,prefix is accepted) or, withcontent_encoding: "text", the text itself, sent as UTF-8. Files over 10 MB after decoding and invalid base64 returninvalid_argument.content_typedefaults to the type of the file extension. Withnote, a note action is added first and the file is linked to it (action_id).hidden_from_user(default true) sets the note'shiddenfromuserand the attachment'sshowforusers. The result is the attachment id, action id, file name, type and size, never the content.halopsa_users_createrefuses (and returns the existing contact) when the email is already used by any contact, active or inactive, and defaultssite_idto the client's main site.halopsa_invoices_list:statusacceptsposted/notposted(sent to HaloPSA);sent,paidand the invoice date range are applied to the latest 200 invoices HaloPSA returns and the result says so.halopsa_lookups_getreturns the identifying fields of each row; for priorities,ticket_priority_idis the value a ticket'spriority_idtakes. A table that fails is reported in place without failing the others.halopsa_sla_getreturns one SLA'sid,nameandpriorities(each withid,name,responsetime,fixtime,colour, whichever HaloPSA sent). Unlikehalopsa_lookups_get(kinds=["priorities"])(a flat list of every priority in the tenant, without timing or colour), this is one SLA's own priority list with the fields Halo stores on it.prioritiesis[], not omitted, when the SLA has none configured.Transient failures (429, 5xx, timeouts) are retried with backoff, honouring
Retry-After; one tool call stays under 120 seconds.
Run locally
uv sync
uv run halopsa-mcp # listens on 0.0.0.0:8080
curl -s http://127.0.0.1:8080/health
curl -s http://127.0.0.1:8080/mcp \
-H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
-H "X-Halo-Client-Id: $HALO_CLIENT_ID" -H "X-Halo-Client-Secret: $HALO_CLIENT_SECRET" \
-H 'X-Halo-Tenant: yourcompany' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Environment variables (all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT
(default 8080), MCP_TRANSPORT (http or stdio). Unknown variables are ignored. Credentials
are never read from the environment.
Docker
docker build -t halopsa-mcp .
docker run --rm -p 8080:8080 halopsa-mcpDevelopment
uv sync
uv run pytest -q
uv run ruff check . && uv run ruff format --check .Code is in src/halopsa_mcp/ (one module per area under tools/), tests in tests/.
The implementation follows the public HaloPSA API documentation at https://halo.halopsa.com/apidoc/
(each instance also serves it at /apidoc/).
License
Copyright 2026 MSPbots.ai. Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.
HaloPSA is a trademark of its owner. This project is not affiliated with or endorsed by Halo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
HaloPSA MCP server for ChatGPT, Claude and any AI agent: list tickets, create ticket, update ticket, add private note, reply to user, log time, search knowledge base and look up client in your own HaloPSA account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to HaloPSA yourself; Cotlet does not store your password and you need no HaloPSA API key. About the official HaloPSA API: HaloPSA has a REST API and its own MCP endpoint (checked 5 Nov 2026). Both need a Halo admin to set up first: an API application under Configuration > Integrations > Halo API, and "Enable the MCP Endpoint" under Configuration > AI > MCP Server. Setup and FAQ: https://cotlet.dev/integrations/halopsa-api-mcp-server
Helpdesk tickets from your AI: find, reply, take, hold, complete — within your own role. OAuth.
Work your HelpRabbit help desk: tickets, replies, customers, the AI agent and its knowledge.
Manage tickets, run agents and workflows, query tables, and search workspace knowledge.
Related MCP Servers
- FlicenseAqualityNot gradedmaintenanceEnables AI assistants to interact with HaloPSA data through secure OAuth2 authentication. Supports SQL queries against the HaloPSA database, API endpoint exploration, and direct API calls for comprehensive PSA data analysis and management.107 npm-
- FlicenseNot gradedqualityDmaintenanceEnables interaction with the HaloPSA API for managing tickets, clients, assets, and more through natural language commands in Claude Desktop.2-
- AlicenseNot gradedqualityDmaintenanceEnables AI-driven IT service management by exposing the full Halo ITSM REST API through 172 tools across 43 resource domains to any MCP-compatible client.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage tickets, users, clients, assets, and more in Halo ITSM through the Model Context Protocol.10MIT