SuperOps + AI in 60 seconds
Unofficial. Community-built Claude Code Skill and MCP server for the SuperOps API. Not affiliated with, endorsed by, or sponsored by SuperOps Inc..
Awaiting live verification - passes every mechanical gate (build, command-surface, claims, install). Be the first to confirm it against your tenant: report it works.
SuperOps unifies PSA and RMM on one database, but the console still answers one entity at a time. Ask your AI “who’s about to breach SLA, and on whose queue,” “what’s the full picture on Acme before the QBR,” or “which endpoints are unpatched and actively alerting,” and get cross-entity answers computed offline from a local SQLite mirror of your tenant - one query instead of five console screens or a scheduled report.
New to the term? An MCP server is the same thing ChatGPT calls an app or connector, Claude on the web calls a connector, and Claude Code calls a Skill. One thing, many names →
Install in 60s → View on GitHub →
Instead of clicking through SuperOps, just ask
Instead of Running a scheduled SLA report, exporting it, and re-sorting by technician in a spreadsheet to spot who is about to miss
just ask: “Who’s about to breach SLA, and on whose queue?”
Your agent runs: superops-cli sla-watch --by tech --window 4h
Instead of Opening the client, then its sites, users, contracts, tickets, assets, and invoices across six console tabs to prep one QBR
just ask: “Give me the full picture on Acme Corp before my 2 o’clock”
Your agent runs: superops-cli client-360 "Acme Corp"
Instead of Cross-checking the patch report against the alert console by hand to find endpoints that are both unpatched and actively alerting
just ask: “Which endpoints are missing a critical patch and actively alerting?”
Your agent runs: superops-cli at-risk-assets --client Acme
See it in 30 seconds
Demo data is simulated. Every command shown exists in the real CLI.
What it does
| Question your MSP keeps asking | Command your agent runs |
|---|---|
| Who’s about to breach SLA, grouped by technician? | superops-cli sla-watch --by tech --window 4h |
| Which clients have alerts still sitting unresolved? | superops-cli alert-coverage --client Acme |
| Which endpoints are missing a critical patch and actively alerting? | superops-cli at-risk-assets --client Acme |
| Which open tickets has nobody touched in a week? | superops-cli stale-tickets --days 7 |
| Everything about one client - sites, users, contracts, tickets, assets, open invoices? | superops-cli client-360 "Acme Corp" |
| Where is billable time concentrated before this month’s invoicing? | superops-cli unbilled --since 2026-05-01 |
| Give my triage agent one ticket with its worklogs, client, and SLA in a single read | superops-cli context-ticket 12345 --agent --select ticket.subject,client.name,sla.name |
| Search every synced ticket, asset, and client for “disk full” | superops-cli search "disk full" |
Full command reference at github.com/servosity/msp-skills/blob/main/skills/superops/guide.md.
What makes this one different
Most SuperOps integrations and MCP servers proxy each question into a live GraphQL call - fine for one record, but an aggregate question becomes a multi-call dance the AI burns context on, and the API rate-limits reads and omits the cross-entity links those questions need. This skill syncs your tenant into a local SQLite mirror with full-text search, so cross-entity questions - SLA breach by tech, client 360, at-risk assets, billable-time reconciliation - become one local join: instant, offline, and the AI sees the answer, not pages of raw JSON.
It complements SuperOps’s own roadmap rather than replacing it: the console stays best for in-app workflows - dispatch, time entry, invoicing - while this skill brings your tenant to whichever AI agent you already use and answers the cross-entity questions, joined across PSA and RMM, that no single console screen composes today.
The pain this closes
- SuperOps unifies PSA and RMM on one database, but the console answers one entity at a time and its own AI features are, in third-party reviews, “more roadmap than reality” (Flamingo, SuperOps Review for MSPs, 2026) - so cross-entity questions like SLA-breach-by-technician or a client’s full footprint still mean clicking across modules or waiting on a scheduled report.
- Reconciling billable time at month-end is manual: the SuperOps list API does not expose a per-entry “already billed” flag, so seeing where billable worklog is concentrated per client - the number you sanity-check before invoicing - means exporting worklogs and totaling them by hand.
- The GraphQL API rate-limits reads and omits some cross-entity links (asset-to-ticket, aggregated child-activity timestamps) from its list payloads, so any script answering “which tickets have gone stale” or “which assets are at risk” has to fetch, cache, and join locally rather than ask the API directly.
Install
Works in any of these agents - pick yours:
| Agent | Quick install |
|---|---|
| Claude Desktop | Step-by-step → |
| ChatGPT (Plus/Pro+) | Step-by-step → |
| Claude Code | Step-by-step → |
| Codex CLI | Step-by-step → |
| Cursor, Windsurf, Cline, Continue, Zed, Copilot, Gemini, Hermes, OpenClaw | Which agent? → |
Quickest path for everyone else (terminal):
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/servosity/msp-skills/main/skills/superops/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/servosity/msp-skills/main/skills/superops/install.ps1 | iex
After install, authenticate once with your SuperOps credentials, then verify with superops-cli --version.
Safety model
| Tier | Examples | Recommended agent policy |
|---|---|---|
| Read | superops-cli sla-watch –by tech –window 4h; superops-cli client-360 “Acme Corp”; superops-cli at-risk-assets –client Acme; superops-cli alert-coverage; superops-cli unbilled –since 2026-05-01; superops-cli stale-tickets –days 7; superops-cli tickets list; superops-cli search “disk full”; superops-cli raw query | Allow |
| Write (mutation escape hatch) | superops-cli raw mutation - the only write path; wraps operations the read-only typed commands don’t cover (createTicket, updateTicket, resolveAlerts). –dry-run prints the exact GraphQL request without sending it | Preview with –dry-run, then a reviewed write |
| Destructive / config | No typed destructive command exists; any irreversible change would have to be an explicit destructive GraphQL operation run through raw mutation (e.g. a delete mutation) | Human-in-the-loop only |
The skill drives the superops-cli and superops-mcp binaries, authenticating with a SUPEROPS_API_TOKEN (plus SUPEROPS_SUBDOMAIN for your tenant) read from the environment - never logged, never sent anywhere except the SuperOps API. Every typed command is read-only: tickets, assets, alerts, clients, contracts, invoices, worklogs, and the cross-entity views change nothing. The single write path is raw mutation; the recommended policy is to preview it with –dry-run, show the exact GraphQL request, get approval, then run. The strongest control is the scope of the API token you mint. Full details in governance.md.
Frequently asked questions
Does this work with ChatGPT?
Yes, on paid ChatGPT plans. ChatGPT connects to remote MCP servers over HTTPS, so you expose the local SuperOps MCP server via a secure bridge. Step-by-step in the install guide.
Do I need to know how to code?
No. Paste one sentence into Claude Code or Codex and your agent does the install, or run a one-line installer. You enter your credentials once.
Is my SuperOps data safe?
Your data stays on your machine. The CLI, MCP server, and the local mirror are all local. The AI sees query results, not raw bulk data, and credentials are never bundled or transmitted by MSP Skills.
Will this hit my SuperOps API rate limits?
The local mirror exists so reads stop hitting the API. After the first sync, the cross-entity views (sla-watch, client-360, at-risk-assets, alert-coverage, unbilled, stale-tickets) run against local SQLite with zero API calls. Live calls respect a --rate-limit throttle, and sync is incremental and resumable - it only fetches what changed, and it treats resources your token can’t reach as warnings, not failures.
Does it work with the US and EU SuperOps regions?
Yes. The US host is the default; set SUPEROPS_REGION=eu to target the EU host (euapi.superops.ai). Your tenant subdomain goes in SUPEROPS_SUBDOMAIN, which the CLI sends as the CustomerSubDomain header on every request.
Can it create or update tickets?
The typed commands are read-only by design - inspection, export, sync, and analysis. The one write path is raw mutation, the supported escape hatch for operations the typed commands don’t wrap (for example createTicket, updateTicket, resolveAlerts). Pair it with –dry-run to preview the exact GraphQL request, and keep a human in the loop; raw query is the read-only counterpart.
What does it cost?
Free. Apache-2.0 licensed. You pay only for whichever AI agent you already use.
Status
Beta. Validated against the SuperOps API surface and being validated with MSPs running it live against their own production tenants in our weekly Build Sessions.
Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).
Maintained by Servosity for the MSP community. Apache-2.0 licensed. Built with CLI Printing Press.