InnerVault

HaloPSA MCP

Stale Official MCP Registry, io.github.Servosity

HaloPSA ticket triage, SLA-breach pre-emption, and cross-client analytics for any MCP agent.

Open the source (opens github.com) https://github.com/servosity/msp-skills

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_OAUTH_SCOPE, HALOPSA_TOKEN. Use a key with the least access you can.

What it is

MCP servers from io.github.Servosity.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

mcpb package (stdio)

https://github.com/Servosity/msp-skills/releases/download/halopsa-v0.2.26/halopsa-mcp.mcpb@0.2.26

From the server's entry in the official MCP Registry

Settings it asks for

  • HALOPSA_BASE_URL · Full API base URL. Leave blank: the CLI builds it from HALOPSA_TENANT and HALOPSA_DOMAIN. Set it only to point at a different host.
  • HALOPSA_CLIENT_ID secret required · OAuth2 client_credentials ID from Configuration → Integrations → Halo PSA API.
  • HALOPSA_CLIENT_SECRET secret required · OAuth2 client_credentials secret.
  • HALOPSA_DOMAIN · Domain template variable. Defaults to halopsa.com.
  • HALOPSA_OAUTH_SCOPE secret required · Sets HALOPSA_OAUTH_SCOPE for the HaloPSA MCP server. Required by the generated client for credential refresh or hand-written auth flow.
  • HALOPSA_SCOPE · Optional. OAuth2 scope (defaults to "all"); set to a narrower scope when your API application requires it
  • HALOPSA_TENANT required · Your HaloPSA tenant identifier.
  • HALOPSA_TOKEN secret · Optional. Pre-issued Bearer access token. Overrides the client_credentials flow when set.
  • HALOPSA_TOKEN_URL · Token endpoint the client-credentials exchange posts to. Leave blank: the CLI derives it from the base URL.
  • HALOPSA_NO_CONFIG_WRITE · Set to 1 to keep credentials off disk. The token cache becomes a no-op, so the connector mints a fresh token each run instead of writing one to config.toml…
  • HALOPSA_MCP_READ_ONLY · Optional. Set to 1 to list only read-only tools.

Related

  1. HaloPSA

    MCP servers

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

    Stale Official MCP Registry, io.github.WYRE-AI Updated 4 days ago 2 notes

    ghcr.io/wyre-ai/halopsa-mcp:v1.8.4
  2. HaloPSA

    MCP servers

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

    Stale Official MCP Registry, io.github.wyre-technology Updated 2 months ago 2 notes

    ghcr.io/wyre-technology/halopsa-mcp:v1.7.11
  3. HaloPSA it service management MCP server: list tickets, create ticket, update ticket.

    Stale Official MCP Registry, dev.cotlet Updated 6 days ago 1 note

  4. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  5. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  6. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0