SuperOps.ai MCP Server

An MCP server for the SuperOps.ai MSP GraphQL API, the combined PSA and RMM. It lets an AI agent read client accounts, tickets, managed assets (with software and patches) and technicians, run read-only GraphQL queries and, on explicit request, create and update tickets, add notes, log time and run custom mutations.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: the API token arrives on every request as an HTTP header and is never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx, graphql-core

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: superops-mcp

Authentication headers

Where to get them:

• Sign in to SuperOps, open the settings icon -> My Profile -> API token and click Generate token. The token acts with that user's permissions, so use an account whose role allows what the agent should do.

• The subdomain is the first part of the tenant's address (yourcompany in yourcompany.superops.ai).

• EU tenants use X-SuperOps-Region: eu (endpoint euapi.superops.ai); everyone else can omit it.

How credentials are sent to SuperOps: every call is a GraphQL POST to https://api.superops.ai/msp (or https://euapi.superops.ai/msp) with Authorization: Bearer <token> and CustomerSubDomain: <subdomain>. Values that look like unresolved templates (${...}) are treated as missing.

A request to /mcp without the token or subdomain gets HTTP 401 naming the missing header. A malformed subdomain or unknown region does not block tools/list; tools then return an invalid_argument error describing the bad header.

Tools

All tools return a JSON string. Lists take page (from 1) and pageSize (default 50, maximum 100) and return SuperOps' listInfo {page, pageSize, totalCount, hasMore}; hasMore is null, not false, on the last page. superops_clients_search, superops_assets_software and superops_assets_patches also take offset (record position from 0, overrides page) and return offset / next_offset: when a page is too large for one response only the records that fit are returned, and next_offset continues right after them (the rest of a cut page is on no other page number).

Ticket status, priority, impact, urgency, category and resolution codes are strings configured per tenant; the stock values are listed in each parameter's description.

Compatibility parameters

The gateway may still send arguments from the older tool contract, so these are accepted and mapped (tests/contract_baseline.json and tests/test_contract.py pin both contracts). When an old and a new form are both given and disagree, the call fails with invalid_argument.

Unknown or ambiguous names and emails fail with invalid_argument before anything is written.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "SuperOps returned HTTP 401: Unauthorized", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. GraphQL errors, which SuperOps returns with HTTP 200, are mapped onto the same codes. Queries are retried with backoff on rate limiting, 5xx and network errors; mutations are retried only on rate limiting, so a write never runs twice.

Run locally

uv sync
uv run python -m superops_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t superops-mcp:dev .
docker run --rm -p 8080:8080 superops-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-SuperOps-API-Token: your-api-token" \
  -H "X-SuperOps-Subdomain: yourcompany" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# open tickets
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-SuperOps-API-Token: your-api-token" \
  -H "X-SuperOps-Subdomain: yourcompany" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"superops_tickets_list","arguments":{"status":["Open"],"pageSize":10}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (22). Kept as is because the tool names are an existing contract; parameters are a superset of the deployed and the upstream contracts (see Compatibility parameters).

• Schema-checked queries. Every GraphQL document was validated against the SuperOps MSP schema published at developer.superops.com.

• Read-only custom queries. superops_custom_query parses the document and refuses mutations, so a read tool cannot write; writes go through superops_custom_mutation, which is annotated destructive and never retried automatically.

• Region. The optional X-SuperOps-Region header reaches EU tenants; without it the US endpoint is used as before.

• Write tools. Ticket create / update / note / time tools change live records (public notes reach the client, billable time can be invoiced); their descriptions tell the agent to use them only on explicit request. qty and unitPrice accept numbers as well as numeric strings.

• No interactive prompts. Older versions asked the user for filters before unfiltered lists, which a stateless gateway cannot relay; lists now page instead.

License

Apache License 2.0 - see LICENSE and NOTICE.