Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • Package no longer on the registry
Own this project? Claim it
HaloPSA logo

HaloPSA

Connects AI agents to HaloPSA for ticket, client, asset, agent, category, and invoice workflows through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install HaloPSA

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "halopsa-2": {
      "command": "npx",
      "args": [
        "-y",
        "@wyre-ai/halopsa-mcp"
      ],
      "env": {
        "HALOPSA_CLIENT_ID": "YOUR_VALUE_HERE",
        "HALOPSA_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "HALOPSA_TENANT": "YOUR_VALUE_HERE",
        "HALOPSA_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The HaloPSA MCP server connects AI clients to the HaloPSA REST API for tickets, clients, assets, agents, teams, categories, and invoices. It starts with navigation and loads domain tools only after a domain is selected, reducing the initial tool set. Run it with HaloPSA OAuth credentials through npm, Docker, or a hosted deployment; use it when an agent needs to inspect or update PSA records. Ticket details can also render as an interactive MCP Apps card in supported hosts such as Claude Desktop and Claude web.

Use cases

  • List and filter open support tickets
  • Create or update HaloPSA tickets
  • Search clients and assets
  • Look up ticket categories for triage
  • Review agents, teams, and invoices

Key features

  • Hierarchical domain-based tool loading
  • Ticket creation, updates, notes, and filtering
  • Client and asset search
  • Category, agent, team, and invoice lookups
  • Interactive ticket cards in MCP Apps hosts
  • OAuth 2.0 configuration through environment variables

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @wyre-ai/halopsa-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
Last commit4d agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How HaloPSA works

What HaloPSA MCP server does

The HaloPSA MCP server exposes selected HaloPSA service-management operations through the Model Context Protocol. It covers support tickets, ticket categories, clients, assets, agents, teams, and invoices. Depending on the domain, an agent can list, search, retrieve, create, update, or annotate records.

Ticket workflows include filtering ticket lists, reading individual tickets, creating tickets, changing existing tickets, and adding notes or actions. Client operations support listing, retrieval, creation, and name-based search. Asset tools provide filtered lists, detail lookup, search, and asset-type discovery. Agents and teams are viewable, while invoice tools provide filtered lists and detail records.

How it works

The HaloPSA MCP server uses hierarchical tool loading rather than presenting every operation immediately. The initial navigation layer provides halopsa_navigate, halopsa_status, and, when applicable, halopsa_back. An agent selects a domain, after which the related tools become available. Domain handlers and the HaloPSA client are loaded when needed.

This model keeps the active tool set focused and gives the agent an explicit navigation state. For example, an agent can enter the tickets domain, list open tickets, return to the main menu, and then enter the clients domain.

The ticket retrieval tool can render an interactive card in MCP Apps hosts, including Claude Desktop and Claude web. The card supports an in-card note action through halopsa_tickets_add_action; other hosts receive the regular JSON behavior.

Setup and configuration

Install the npm package from GitHub Packages after authenticating npm with a GitHub token that has the read:packages scope. The package can then be started with npx @wyre-ai/halopsa-mcp. A Docker image can also be built locally and run with the required credentials.

Set HALOPSA_CLIENT_ID and HALOPSA_CLIENT_SECRET for OAuth 2.0 authentication. Provide either HALOPSA_TENANT, such as yourcompany, or HALOPSA_BASE_URL with the explicit HaloPSA URL. Cloud build deployments also need package-registry authentication: Cloudflare Workers uses NODE_AUTH_TOKEN, while DigitalOcean App Platform uses a build-time GITHUB_TOKEN.

The DigitalOcean target runs the complete MCP server over HTTP. The Cloudflare Workers target currently exposes a thin entrypoint whose /mcp route returns HTTP 501 until its Workers transport adapter is available.

Tools and capabilities

Available domains and representative operations include:

  • Tickets: list, get, create, update, and add actions or notes.
  • Categories: list a page of categories or retrieve one by ID.
  • Clients: list, get, create, and search by name.
  • Assets: list with filters, get, search, and list asset types.
  • Agents: list agents, get an agent, and list teams.
  • Invoices: list with filters and get invoice details.

Ticket listing accepts category_1 filtering; deeper category filters are rejected for that operation. Category lookup helps assign category levels when creating or updating tickets.

Limitations and notes

HaloPSA applies a limit of 500 requests per three-minute window. The underlying client performs request throttling automatically. The HaloPSA MCP server requires valid HaloPSA OAuth credentials and package access during npm installation. Interactive ticket cards depend on an MCP Apps-capable host; clients without that support receive plain JSON results. The project is licensed under Apache-2.0.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about HaloPSA

HaloPSA is an MCP server that connects AI clients to the HaloPSA REST API. Its main tools manage tickets, clients, assets, categories, agents, teams, and invoices, with operations for listing, searching, retrieving, creating, updating, and adding ticket notes or actions through a navigable domain-based interface.

Authenticate npm with GitHub Packages using a token with the read:packages scope, then run `npm install @wyre-ai/halopsa-mcp` or start it with `npx @wyre-ai/halopsa-mcp`. The package's repository configuration reads the token from `NODE_AUTH_TOKEN`.

Set `HALOPSA_CLIENT_ID` and `HALOPSA_CLIENT_SECRET`, plus either `HALOPSA_TENANT` or `HALOPSA_BASE_URL`. The tenant identifies the HaloPSA account, while the base URL supplies an explicit service endpoint.

Yes, HaloPSA works with Claude Desktop through its standard MCP configuration. Add the package as an `npx` command and pass the client ID, client secret, and tenant in the server's environment settings.

Yes, you can build the Docker image locally and run it with `HALOPSA_CLIENT_ID`, `HALOPSA_CLIENT_SECRET`, and `HALOPSA_TENANT` environment variables. A prebuilt container image is also identified in the project documentation.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHaloPSA AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/halopsa-2?style=directory)](https://allmcps.com/mcp/halopsa-2)
HTML Embed
<a href="https://allmcps.com/mcp/halopsa-2"><img src="https://allmcps.com/api/badge/halopsa-2?style=directory" alt="HaloPSA on AllMCPs" /></a>