Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • Package no longer on the registry
Own this project? Claim it
SuperOps logo

SuperOps

Connects AI clients to SuperOps.ai for managing clients, tickets, assets, technicians, and custom GraphQL operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install SuperOps

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "superops": {
      "command": "npx",
      "args": [
        "@wyre-ai/superops-mcp"
      ],
      "env": {
        "SUPEROPS_API_TOKEN": "YOUR_VALUE_HERE",
        "SUPEROPS_SUBDOMAIN": "YOUR_VALUE_HERE",
        "SUPEROPS_REGION": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The SuperOps MCP server connects AI clients to the SuperOps.ai PSA/RMM platform through its GraphQL API. It exposes domain-specific tools for clients, tickets, assets, technicians, navigation, connection testing, and custom GraphQL queries or mutations. Use it when an agent needs to inspect or modify SuperOps records, manage tickets, review endpoint data, or work with API operations beyond the standard tools.

Use cases

  • List open or filtered support tickets
  • Create and update SuperOps tickets
  • Review endpoint software and patch status
  • Search for clients by name
  • Run custom SuperOps GraphQL operations

Key features

  • Client, ticket, asset, and technician tools
  • Ticket creation, updates, notes, and time logging
  • Software inventory and patch status lookup
  • Custom GraphQL queries and mutations
  • Page-based pagination and composable filters
  • Interactive ticket cards in MCP Apps hosts

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 42d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 23h ago via OSV.dev · @wyre-ai/superops-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
Last commit4d agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How SuperOps works

What the SuperOps MCP server does

The SuperOps MCP server gives MCP clients access to SuperOps.ai, a PSA/RMM platform. Its tools cover client records, service tickets, managed assets or endpoints, software and patch inventory, and technician information. Ticket tools support creating tickets, updating status or assignment, adding notes, and logging time.

The server also provides navigation and connectivity tools. Agents can select a domain, return to the main menu, or test access to the SuperOps API before making operational requests.

How it works

The SuperOps MCP server communicates with SuperOps.ai through the platform’s GraphQL API. Its decision-tree design starts with domain navigation, while domain modules load when needed. This lazy-loading approach keeps the initial startup smaller and exposes tools relevant to the selected area.

Standard list operations use page-based pagination. Requests accept a 1-indexed page and a pageSize from 1 to 100, with 50 as the default. Responses include page information, total results, and a hasMore value. A hasMore value of null means there are no additional pages; it never returns false.

For operations that need API behavior not represented by the built-in tools, custom GraphQL query and mutation tools are available. Ticket retrieval can also render an interactive card in MCP Apps hosts such as Claude Desktop or Claude web. Its add-note action always creates an internal note rather than a public reply.

Setup and configuration

Install the package from GitHub Packages with npm:

server.ts
export NODE_AUTH_TOKEN=$(gh auth token)
npm install @wyre-ai/superops-mcp

GitHub Packages requires authentication even for this public package. Cloud deployments need a package token during the build: Cloudflare Workers uses NODE_AUTH_TOKEN, while DigitalOcean App Platform uses a build-time GITHUB_TOKEN secret.

The SuperOps MCP server requires these runtime variables:

  • SUPEROPS_API_TOKEN: an API token generated from the API token tab in the SuperOps.ai profile settings.
  • SUPEROPS_SUBDOMAIN: the tenant subdomain.
  • SUPEROPS_REGION: us or eu.

A Claude Desktop configuration can launch the server with npx and pass these values in its env object.

Tools and capabilities

Available tool groups include:

  • Navigation and API connectivity testing.
  • Client listing, lookup, and name search.
  • Ticket listing, retrieval, creation, updates, notes, and time entries.
  • Asset listing and retrieval, plus software inventory and patch status.
  • Technician listing, detail lookup, and group listing.
  • Custom GraphQL queries and mutations.

Ticket cards can be branded without rebuilding by using the documented MCP_BRAND_* variables or a window.__BRAND__ injection. Other hosts receive the ordinary JSON behavior.

Limitations and notes

The SuperOps API allows 800 requests per minute per API token. Filters use condition clauses with operators such as is, contains, startsWith, includes, and their negative forms. equals and in are not accepted. Filtering with an invalid field value, or against a JSON column instead of a nested path, can silently return zero rows.

For complex filter behavior, use the custom query tool. The repository includes a GraphQL schema and validates its documents against that schema during tests; the schema should be regenerated after an API change. The project is licensed under Apache-2.0.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about SuperOps

SuperOps is an MCP server that connects AI clients to the SuperOps.ai PSA/RMM platform through its GraphQL API. Its main tools cover clients, tickets, assets, technicians, navigation, connection testing, and custom GraphQL queries or mutations, with ticket creation, updates, notes, and time logging included.

Install it with npm after authenticating to GitHub Packages. Set `NODE_AUTH_TOKEN`, then run `npm install @wyre-ai/superops-mcp`; cloud deployments must provide the corresponding package token as a build-time credential.

Add the package as an `npx` MCP server in `claude_desktop_config.json` and provide `SUPEROPS_API_TOKEN`, `SUPEROPS_SUBDOMAIN`, and `SUPEROPS_REGION` in the server’s environment configuration.

It can list and retrieve tickets, create tickets, update status or assignment, add notes, and log time. In Claude Desktop or Claude web, ticket retrieval can also render an interactive card with an internal-only add-note action.

Pagination uses 1-indexed pages rather than cursors. Set `page` and `pageSize`, with a maximum page size of 100, and continue while `hasMore` is `true`; the API uses `null` when no additional page exists.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSuperOps AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/superops?style=directory)](https://allmcps.com/mcp/superops)
HTML Embed
<a href="https://allmcps.com/mcp/superops"><img src="https://allmcps.com/api/badge/superops?style=directory" alt="SuperOps on AllMCPs" /></a>