InnerVault

SuperOps MCP

Stale Official MCP Registry, io.github.Servosity

Every SuperOps PSA+RMM entity in your terminal, plus a local SQLite mirror that answers

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: PRINTING_PRESS_CLIENT_PROFILE, SUPEROPS_API_TOKEN, SUPEROPS_MCP_HTTP_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/superops-v0.1.19/superops-mcp.mcpb@0.1.19

From the server's entry in the official MCP Registry

Settings it asks for

  • SUPEROPS_API_TOKEN secret required · Set the SUPEROPS_API_TOKEN credential for the SuperOps MCP server.
  • SUPEROPS_BASE_URL · Base URL for the SuperOps API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
  • SUPEROPS_REGION · Data-centre region your tenant lives in: us or eu. The wrong region answers with an authentication error.
  • SUPEROPS_SUBDOMAIN required · Your tenant subdomain (SuperOps: Settings > MSP Information). Sent as the CustomerSubdomain header on every call; requests without it are rejected.
  • SUPEROPS_MCP_READ_ONLY · Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing call.
  • SUPEROPS_NO_LOCAL_DATA · Optional. Set to 1 to save no API data locally: sync and workflow archive are refused and the response cache is off.
  • SUPEROPS_MCP_HTTP_TOKEN secret · Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
  • SUPEROPS_USER_AGENT · Optional. Overrides the User-Agent the CLI sends to SuperOps. Leave blank to use the built-in one.
  • PRINTING_PRESS_CLIENT_PROFILE secret · Only used when the MCP server is bound to a tenant-gated client profile. This connector registers no tenant-gated source, so leave it blank.

Related

  1. SuperOps

    MCP servers

    MCP server for SuperOps unified PSA+RMM — clients, tickets, assets, and more.

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

    ghcr.io/wyre-ai/superops-mcp:v2.0.4
  2. SuperOps

    MCP servers

    MCP server for SuperOps unified PSA+RMM — clients, tickets, assets, and more.

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

    ghcr.io/wyre-technology/superops-mcp:v1.6.6
  3. 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/
  4. 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

  5. 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

  6. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

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