Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
docker run -i --rm ghcr.io/wyre-ai/halopsa-mcp:v1.8.4Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
HALOPSA_CLIENT_ID=<value> HALOPSA_CLIENT_SECRET=<secret> HALOPSA_TENANT=<value> HALOPSA_BASE_URL=<value> MCP_TRANSPORT=<value> AUTH_MODE=<value> LOG_LEVEL=<value> claude mcp add io.github.wyre-ai-halopsa-mcp -- docker run -i --rm ghcr.io/wyre-ai/halopsa-mcp:v1.8.4Run in a terminal.
{ "mcpServers": { "io.github.wyre-ai-halopsa-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/wyre-ai/halopsa-mcp:v1.8.4" ], "env": { "HALOPSA_CLIENT_ID": "<value>", "HALOPSA_CLIENT_SECRET": "<secret>", "HALOPSA_TENANT": "<value>", "HALOPSA_BASE_URL": "<value>", "MCP_TRANSPORT": "<value>", "AUTH_MODE": "<value>", "LOG_LEVEL": "<value>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
A Model Context Protocol (MCP) server for interacting with HaloPSA, featuring a decision tree architecture for efficient tool loading.
[!IMPORTANT] Before you click: this server depends on , which is hosted on the npm registry. GitHub Packages has no anonymous access — even though the package is public, every needs a token. The cloud builder runs for you, so you must give it one, or the build fails with .
MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.
@wyre-technology/node-halopsanpm installnpm installnpm error 401 Unauthorized ... npm.pkg.github.comread:packages scope
(classic token).
Any GitHub account works — you do not need to be a member of the
wyre-technology org to read its public packages.NODE_AUTH_TOKEN to your PAT
(Workers → Settings → Build → Variables and Secrets).GITHUB_TOKEN
with scope Build Time to your PAT (the .do/app.yaml already declares it).
[!NOTE] The DigitalOcean target builds the full Docker image and runs the complete MCP server over HTTP — this is the recommended path for operators. The Cloudflare Workers target is currently a thin entrypoint (the
/mcproute returns 501 until the Workers transport adapter lands) and is best suited to gateway-style deployments; for a full self-hosted server prefer DigitalOcean or the prebuilt container image (ghcr.io/wyre-ai/halopsa-mcp).
This MCP server uses a hierarchical tool loading approach instead of exposing all tools upfront:
halopsa_navigate)This architecture provides:
halopsa_tickets_get renders as an interactive card in MCP Apps hosts
(Claude Desktop/web) with an in-card "Add note" round-trip via
halopsa_tickets_add_action; plain-JSON behavior is unchanged in other hosts.
The card is neutral by default and brandable via window.__BRAND__ injection
or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL,
MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG,
MCP_BRAND_TEXT) — no rebuild needed.
This package is published to the GitHub Packages npm registry, which requires a token even for public packages. Authenticate once, then install:
# Authenticate npm to GitHub Packages (token needs the read:packages scope)
export NODE_AUTH_TOKEN=$(gh auth token) # or a PAT with read:packages
npm install @wyre-ai/halopsa-mcp
The repo's .npmrc already points the @wyre-technology scope at GitHub Packages and
reads the token from NODE_AUTH_TOKEN, so no further config is needed.
Set the following environment variables:
# Set credentials
export HALOPSA_CLIENT_ID="your-client-id"
export HALOPSA_CLIENT_SECRET="your-client-secret"
export HALOPSA_TENANT="yourcompany"
# Run the server
npx @wyre-ai/halopsa-mcp
Add to your Claude Desktop claude_desktop_config.json:
{
"mcpServers": {
"halopsa": {
"command": "npx",
"args": ["@wyre-ai/halopsa-mcp"],
"env": {
"HALOPSA_CLIENT_ID": "your-client-id",
"HALOPSA_CLIENT_SECRET": "your-client-secret",
"HALOPSA_TENANT": "yourcompany"
}
}
}
}
docker build -t halopsa-mcp .
docker run -e HALOPSA_CLIENT_ID=xxx -e HALOPSA_CLIENT_SECRET=xxx -e HALOPSA_TENANT=yourcompany halopsa-mcp
Manage support tickets, create new tickets, update status, add actions/notes.
Tools:
halopsa_tickets_list - List tickets with filters (category_1 only; category_2–category_4 are rejected)halopsa_tickets_get - Get ticket detailshalopsa_tickets_create - Create a new ticket (optional category_1–category_4)halopsa_tickets_update - Update an existing ticket (optional category_1–category_4)halopsa_tickets_add_action - Add a note/action to a ticketLook up Halo ticket categories so triage can assign category_1–category_4 (the category name, matched to its level).
Tools:
halopsa_categories_list - List one page of ticket categories (limit defaults to 50; page_no starts at 1)halopsa_categories_get - Get a category by IDManage companies/clients in HaloPSA.
Tools:
halopsa_clients_list - List clientshalopsa_clients_get - Get client detailshalopsa_clients_create - Create a new clienthalopsa_clients_search - Search clients by nameManage configuration items/assets.
Tools:
halopsa_assets_list - List assets with filtershalopsa_assets_get - Get asset detailshalopsa_assets_search - Search assetshalopsa_assets_list_types - List available asset typesView technicians and teams.
Tools:
halopsa_agents_list - List agents/technicianshalopsa_agents_get - Get agent detailshalopsa_teams_list - List teamsView billing and invoices.
Tools:
halopsa_invoices_list - List invoices with filtershalopsa_invoices_get - Get invoice detailsAlways available:
halopsa_navigate - Select a domain to work withhalopsa_status - Show current state and credential statushalopsa_back - Return to main menu (when in a domain)User: Check my tickets
Claude: [calls halopsa_navigate with domain="tickets"]
-> Navigated to tickets domain. Available tools: ...
User: List open tickets
Claude: [calls halopsa_tickets_list with open_only=true]
-> [ticket list results]
User: Now show me clients
Claude: [calls halopsa_back]
-> Navigated back to main menu.
[calls halopsa_navigate with domain="clients"]
-> Navigated to clients domain.
HaloPSA has a rate limit of 500 requests per 3-minute window. The underlying @asachs01/node-halopsa client handles this automatically with request throttling.
Apache-2.0
© 2026 MCP Directory.
MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.
{ "mcpServers": { "io.github.wyre-ai-halopsa-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/wyre-ai/halopsa-mcp:v1.8.4" ], "env": { "HALOPSA_CLIENT_ID": "<value>", "HALOPSA_CLIENT_SECRET": "<secret>", "HALOPSA_TENANT": "<value>", "HALOPSA_BASE_URL": "<value>", "MCP_TRANSPORT": "<value>", "AUTH_MODE": "<value>", "LOG_LEVEL": "<value>" } } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL.
HaloPSA runs locally over stdio.
Last checked 2026-11-15. MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.