SuperOps MSP MCP Server

An MCP server that gives AI assistants full access to the SuperOps MSP GraphQL API through two dynamic tools powered by live schema introspection.

What is SuperOps MSP?

SuperOps MSP is for Managed Service Providers - IT companies that manage technology for multiple client businesses. Key concepts:

• Multi-tenant: One MSP serves many clients
• Client-based: Data organized by Client → Site → Assets/Tickets
• Billing included: Invoice and billing features for client management

Installation

bunx superops-msp@latest

Or with npx:

npx superops-msp@latest

Configuration

Claude Code

claude mcp add superops-msp \
  -e SUPEROPS_API_KEY=your-api-key \
  -e SUPEROPS_SUBDOMAIN=your-subdomain \
  -- bunx superops-msp@latest

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "superops-msp": {
      "command": "bunx",
      "args": ["superops-msp@latest"],
      "env": {
        "SUPEROPS_API_KEY": "your-api-key",
        "SUPEROPS_SUBDOMAIN": "your-subdomain"
      }
    }
  }
}

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | SUPEROPS_API_KEY | Yes | Your SuperOps API key | | SUPEROPS_SUBDOMAIN | Yes | Your subdomain (e.g., acme from acme.superops.ai) | | SUPEROPS_REGION | No | us (default) or eu | | SUPEROPS_TIMEOUT | No | Request timeout in ms (default: 30000) | | SUPEROPS_READ_ONLY | No | Set to true to block mutations |

Get your API key from SuperOps Admin > API Settings.

Tools

superops-api

Execute any SuperOps API operation by name. The server builds the GraphQL query automatically from the introspected schema.

superops-api({ operation: "getPriorityList" })

superops-api({
  operation: "getTicket",
  params: { ticketId: "25507674456317952" }
})

superops-api({
  operation: "getTicketList",
  params: { page: 1, pageSize: 10 }
})

superops-api({
  operation: "createTicket",
  params: {
    subject: "Printer not working",
    requestType: "Incident",
    clientId: "12345"
  }
})

superops-api-schema

Discover available operations and their parameter schemas. Four modes:

Category summary (no params):

superops-api-schema()
→ Lists all categories with operation counts

Category detail:

superops-api-schema({ category: "Ticket" })
→ Lists all ticket operations with descriptions

Operation detail:

superops-api-schema({ operation: "getTicket" })
→ Full parameter schema, argument types, return fields

Usage examples:

superops-api-schema({ examples: true })
→ All usage patterns, gotchas, and ID field conventions

superops-api-schema({ operation: "getTicketList", examples: true })
→ Operation schema + specific usage example with filtering patterns

API Coverage

The server exposes every operation available in the SuperOps MSP GraphQL API — currently 169 operations (97 queries + 72 mutations) including:

• Tickets, conversations, notes
• Assets, software, patches, disks, alerts
• Clients, sites, contacts, contracts
• Invoices, quotes, taxes
• Knowledge base articles and collections
• Scripts and execution
• Worklogs and time tracking
• Webhooks and subscriptions
• Approvals and SLAs
• Service catalog items
• IT documentation
• Technicians, teams, groups, roles

Operations are discovered via live GraphQL introspection. When SuperOps adds new API operations, they're available immediately.

Transport

The server supports three transport modes:

| Mode | Flag | Use Case | |------|------|----------| | stdio | (default) | Claude Code, Claude Desktop | | Streamable HTTP | --http | Web clients, containers | | Legacy SSE | --sse | Older MCP clients |

HTTP mode exposes /mcp (Streamable HTTP), /sse + /messages (legacy), and /health.

API Limits

• Maximum 800 API requests per minute
• Date/time values must be in UTC with ISO format (e.g., 2026-03-17T10:15:30)
• Use null to clear/reset attribute values

API Endpoints

• US: https://api.superops.ai/msp
• EU: https://euapi.superops.ai/msp

Related

• superops-it - For SuperOps IT Teams (internal IT departments)

License

MIT