HaloPSA

Name: HaloPSA
Author: WYRE-AI

by WYRE-AIversion 1.8.2i★ –iRuns on your computer

Registry nameio.github.WYRE-AI/halopsa-mcp

Install

Overview

Description from the maker (original English)

MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "halopsa": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HALOPSA_CLIENT_ID",
        "-e",
        "HALOPSA_CLIENT_SECRET",
        "-e",
        "HALOPSA_TENANT",
        "-e",
        "HALOPSA_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"
      ],
      "env": {
        "HALOPSA_CLIENT_ID": "your-value",
        "HALOPSA_CLIENT_SECRET": "your-value",
        "HALOPSA_TENANT": "your-value",
        "HALOPSA_BASE_URL": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add halopsa --env HALOPSA_CLIENT_ID=your-value --env HALOPSA_CLIENT_SECRET=your-value --env HALOPSA_TENANT=your-value --env HALOPSA_BASE_URL=your-value --env MCP_TRANSPORT=your-value --env AUTH_MODE=your-value --env LOG_LEVEL=your-value -- docker run -i --rm -e HALOPSA_CLIENT_ID -e HALOPSA_CLIENT_SECRET -e HALOPSA_TENANT -e HALOPSA_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/halopsa-mcp:v1.8.2

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "halopsa": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HALOPSA_CLIENT_ID",
        "-e",
        "HALOPSA_CLIENT_SECRET",
        "-e",
        "HALOPSA_TENANT",
        "-e",
        "HALOPSA_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"
      ],
      "env": {
        "HALOPSA_CLIENT_ID": "your-value",
        "HALOPSA_CLIENT_SECRET": "your-value",
        "HALOPSA_TENANT": "your-value",
        "HALOPSA_BASE_URL": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "halopsa": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "HALOPSA_CLIENT_ID",
        "-e",
        "HALOPSA_CLIENT_SECRET",
        "-e",
        "HALOPSA_TENANT",
        "-e",
        "HALOPSA_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"
      ],
      "env": {
        "HALOPSA_CLIENT_ID": "your-value",
        "HALOPSA_CLIENT_SECRET": "your-value",
        "HALOPSA_TENANT": "your-value",
        "HALOPSA_BASE_URL": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

HALOPSA_CLIENT_ID required env
HaloPSA OAuth client ID
HALOPSA_CLIENT_SECRET secret required env
HaloPSA OAuth client secret
HALOPSA_TENANT env
HaloPSA tenant identifier (subdomain). Provide this or HALOPSA_BASE_URL.
HALOPSA_BASE_URL env
HaloPSA base URL (e.g. https://your-instance.halopsa.com). Provide this or HALOPSA_TENANT.
MCP_TRANSPORT env
Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
AUTH_MODE env
Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
LOG_LEVEL env
Log verbosity: debug, info, warn, error

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account WYRE-AI, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18380 servers in this category
Published to the registry more recently than 67% of the other 18380 servers in this category
Basic checks equal to or better than 100% of the other 18380 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is HaloPSA safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.8.2) reached the registry 22 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Tethered Trust

by tetheredtrust.com

Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

HaloPSA MCP Server

A Model Context Protocol (MCP) server for interacting with HaloPSA, featuring a decision tree architecture for efficient tool loading.

One-Click Deployment

[!IMPORTANT]

Before you click: this server depends on @wyre-technology/node-halopsa,

which is hosted on the GitHub Packages npm registry. GitHub Packages has no

anonymous access — even though the package is public, every npm install needs a

token. The cloud builder runs npm install for you, so you must give it one, or

the build fails with npm error 401 Unauthorized ... npm.pkg.github.com.

1. Create a GitHub Personal Access Token with the read: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.

2. Add it as a build variable when prompted by the deploy flow:

- Cloudflare Workers → set a build variable named `NODE_AUTH_TOKEN` to your PAT

(Workers → Settings → Build → Variables and Secrets).

- DigitalOcean App Platform → set an encrypted env var named `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 /mcp route 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).

Architecture

This MCP server uses a hierarchical tool loading approach instead of exposing all tools upfront:

Navigation Phase: Initially exposes only a navigation tool (halopsa_navigate)
Domain Selection: User selects a domain (tickets, clients, assets, agents, invoices, categories)
Domain Tools: Server exposes domain-specific tools after selection
Lazy Loading: Domain handlers and the HaloPSA client are loaded on-demand

This architecture provides:

Reduced cognitive load (fewer tools to choose from)
Faster initial load times
Better organization of related operations
Clear navigation state

Interactive Ticket Card (MCP Apps)

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.

Installation

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.

Configuration

Set the following environment variables:

Variable	Required	Description
`HALOPSA_CLIENT_ID`	Yes	OAuth 2.0 Client ID
`HALOPSA_CLIENT_SECRET`	Yes	OAuth 2.0 Client Secret
`HALOPSA_TENANT`	One of	Tenant name (e.g., `yourcompany`)
`HALOPSA_BASE_URL`	these	Explicit base URL (e.g., `https://yourcompany.halopsa.com`)

Usage

Running Standalone

# 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

Claude Desktop Configuration

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

docker build -t halopsa-mcp .

docker run -e HALOPSA_CLIENT_ID=xxx -e HALOPSA_CLIENT_SECRET=xxx -e HALOPSA_TENANT=yourcompany halopsa-mcp

Available Domains

Tickets

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 details
halopsa_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 ticket

Clients

Manage companies/clients in HaloPSA.

Tools:

halopsa_clients_list - List clients
halopsa_clients_get - Get client details
halopsa_clients_create - Create a new client
halopsa_clients_search - Search clients by name

Assets

Manage configuration items/assets.

Tools:

halopsa_assets_list - List assets with filters
halopsa_assets_get - Get asset details
halopsa_assets_search - Search assets
halopsa_assets_list_types - List available asset types

Agents

View technicians and teams.

Tools:

halopsa_agents_list - List agents/technicians
halopsa_agents_get - Get agent details
halopsa_teams_list - List teams

Invoices

View billing and invoices.

Tools:

halopsa_invoices_list - List invoices with filters
halopsa_invoices_get - Get invoice details

Navigation Tools

Always available:

halopsa_navigate - Select a domain to work with
halopsa_status - Show current state and credential status
halopsa_back - Return to main menu (when in a domain)

Example Workflow

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.

Rate Limiting

HaloPSA has a rate limit of 500 requests per 3-minute window. The underlying @asachs01/node-halopsa client handles this automatically with request throttling.

License

Apache-2.0

HaloPSA

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Tethered Trust

README from the maker

HaloPSA MCP Server

One-Click Deployment

Architecture

Interactive Ticket Card (MCP Apps)

Installation

Configuration

Usage

Running Standalone

Run the server

Claude Desktop Configuration

Docker

Available Domains

Tickets

Categories

Clients

Assets

Agents

Invoices

Navigation Tools

Example Workflow

Rate Limiting

License