SuperOps MCP
SuperOps PSA and RMM users who want every platform entity queryable from the terminal with a local SQLite mirror for fast agent answers.
Overview
SuperOps MCP is a MCP server for the Operate phase that surfaces SuperOps PSA and RMM entities plus a local SQLite mirror for terminal-based agent workflows.
What is this MCP server?
- Exposes SuperOps PSA and RMM entities to MCP agents over stdio
- Local SQLite mirror for repeated queries and lower-latency agent workflows
- Terminal-oriented access pattern for tickets, assets, and MSP operational records
- Single required credential: SUPEROPS_API_TOKEN
- mcpb release superops-mcp v0.1.0 from Servosity msp-skills
- Server version 0.1.0
- Transport: stdio via mcpb package
- One required secret: SUPEROPS_API_TOKEN
Community signal: 1 GitHub stars.
What problem does it solve?
SuperOps users waste context switching when agents cannot read PSA and RMM records unless someone copies fields out of the web UI.
Who is it for?
SuperOps customers who want Claude Code or Cursor to draft ticket updates, asset lookups, and client summaries from live MSP data.
Skip if: MSPs on ConnectWise, Halo, or other stacks without SuperOps, or solo builders with no PSA/RMM practice.
What do I get? / Deliverables
After API token setup, your agent can query SuperOps entities and leverage the SQLite mirror for faster operational answers in the same session.
- Agent-accessible SuperOps PSA and RMM entity queries
- Local SQLite datastore synchronized for mirrored operational data
- Faster repeated MSP operational lookups without full UI context switches
Recommended MCP Servers
Journey fit
PSA tickets, RMM assets, and client records are core production operations data for MSPs managing live customer environments. Infra reflects the SQLite mirror and full entity API access that underpin day-to-day MSP service delivery tooling in the agent.
How it compares
SuperOps PSA+RMM MCP terminal bridge, not a generic SQLite or Git MCP server.
Common Questions / FAQ
Who is SuperOps MCP for?
It is for teams using SuperOps PSA and RMM with an API token who want MCP agents to read and analyze operational entities locally.
When should I use SuperOps MCP?
Use it during operate-phase ticket triage, asset checks, or when you need cached SQLite-backed answers while working in your coding agent.
How do I add SuperOps MCP to my agent?
Install superops-mcp mcpb v0.1.0, set SUPEROPS_API_TOKEN in the server environment, and register the stdio MCP entry in your client configuration.