SuperOps MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SuperOps MCP Server show open high priority tickets"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SuperOps.ai MCP Server
MCP server for Claude that provides tools to interact with the SuperOps.ai PSA/RMM platform using their GraphQL API.
One-Click Deployment
Operator note — GitHub Packages authentication. This package is published to the
@wyre-technologyscope on GitHub Packages, which requires an authentication token on every install (GitHub Packages has no anonymous reads, even for public packages). Create a GitHub Personal Access Token with theread:packagesscope and supply it to the cloud builder:
Cloudflare Workers — set a build variable named
NODE_AUTH_TOKENto your PAT.DigitalOcean App Platform — set a build-time secret named
GITHUB_TOKENto your PAT.For local installs, run
export NODE_AUTH_TOKEN=$(gh auth token)beforenpm install.
Related MCP server: Sophos Central MCP Server
Features
Decision Tree Architecture: Navigate to domains (clients, tickets, assets, technicians) to see relevant tools
Lazy Loading: Domain modules load on-demand for faster startup
Full CRUD Operations: List, get, create, and update entities
GraphQL Support: Use custom queries for advanced operations
Installation
# The @wyre-technology scope lives on GitHub Packages and needs a token to install:
export NODE_AUTH_TOKEN=$(gh auth token)
npm install @wyre-technology/superops-mcpConfiguration
Set the following environment variables:
export SUPEROPS_API_TOKEN="your-api-token"
export SUPEROPS_SUBDOMAIN="yourcompany"
export SUPEROPS_REGION="us" # or "eu" for EU regionGetting Your API Token
Log in to SuperOps.ai
Click settings icon > "My Profile"
Navigate to "API token" tab
Click "Generate token"
Copy and securely store the token
Usage with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"superops": {
"command": "npx",
"args": ["@wyre-technology/superops-mcp"],
"env": {
"SUPEROPS_API_TOKEN": "your-api-token",
"SUPEROPS_SUBDOMAIN": "yourcompany",
"SUPEROPS_REGION": "us"
}
}
}
}Available Domains & Tools
Navigation
superops_navigate- Navigate to a domainsuperops_back- Return to main menusuperops_test_connection- Test API connectivity
Clients Domain
superops_clients_list- List clients with filterssuperops_clients_get- Get client detailssuperops_clients_search- Search clients by name/domain
Tickets Domain
superops_tickets_list- List tickets with filterssuperops_tickets_get- Get ticket detailssuperops_tickets_create- Create a new ticketsuperops_tickets_update- Update ticket status/assignmentsuperops_tickets_add_note- Add note to ticketsuperops_tickets_log_time- Log time on ticket
Assets Domain
superops_assets_list- List assets/endpointssuperops_assets_get- Get asset detailssuperops_assets_software- Get software inventorysuperops_assets_patches- Get patch status
Technicians Domain
superops_technicians_list- List technicianssuperops_technicians_get- Get technician detailssuperops_technicians_groups- List technician groups
Custom Domain
superops_custom_query- Run custom GraphQL querysuperops_custom_mutation- Run custom GraphQL mutation
Example Usage
User: What tools are available?
Claude: Use superops_navigate to select a domain...
User: Navigate to tickets
Claude: [calls superops_navigate with domain: "tickets"]
Now in tickets domain. Available tools: superops_tickets_list, superops_tickets_get...
User: Show open high priority tickets
Claude: [calls superops_tickets_list with status: ["Open"], priority: ["High"]]
Here are the open high priority tickets...Rate Limits
SuperOps.ai API has a rate limit of 800 requests per minute per API token.
License
Apache-2.0
Support
For issues and feature requests, please visit the GitHub repository.
Available Tools
21 toolssuperops_assets_getA
Get detailed information for a specific asset including hardware, OS, and network details.
Inputs: assetId (required).
superops_assets_listA
List assets (endpoints) in SuperOps.ai RMM. Can filter by status, platform, or client.
Inputs: max, cursor, status, clientId, +1 more.
superops_assets_patchesA
Get patch status and pending patches for a specific asset.
Inputs: assetId (required), status, severity.
superops_assets_softwareA
Get the software inventory for a specific asset.
Inputs: assetId (required), max, search.
superops_clients_getA
Get detailed information for a specific client by their account ID.
Inputs: accountId (required).
superops_clients_listA
List clients (accounts) in SuperOps.ai. Can filter by status, stage, or paginate through results.
Inputs: max, stage, cursor, status.
superops_clients_searchA
Search for clients by name or email domain. Returns matching clients with basic information.
Inputs: query (required), max.
superops_custom_mutationB
Run a custom GraphQL mutation against the SuperOps.ai API. For advanced write operations not covered by standard tools.
Inputs: mutation (required), variables.
superops_custom_queryA
Run a custom GraphQL query against the SuperOps.ai API. For advanced use cases not covered by standard tools.
Inputs: query (required), variables.
superops_statusB
Show credentials status and available domains
Inputs: no named parameters.
superops_technicians_getA
Get detailed information for a specific technician by their ID.
Inputs: technicianId (required).
superops_technicians_groupsB
List technician groups/teams in SuperOps.ai.
Inputs: max.
superops_technicians_listB
List technicians (agents) in SuperOps.ai. Can filter by active status or team.
Inputs: max, cursor, teamId, activeOnly.
superops_test_connectionA
Test the connection to SuperOps.ai API using configured credentials.
Inputs: no named parameters.
superops_tickets_add_noteA
Add a note to a ticket. Can be internal or public (visible to client).
Inputs: content (required), ticketId (required), isPublic.
superops_tickets_createC
Create a new ticket in SuperOps.ai.
Inputs: subject (required), clientId (required), priority, description, +3 more.
superops_tickets_getA
Get detailed information for a specific ticket by its ID.
Inputs: ticketId (required).
superops_tickets_listB
List tickets in SuperOps.ai. Can filter by status, priority, client, or assignee.
Inputs: max, cursor, status, clientId, +3 more.
superops_tickets_log_timeB
Log time spent on a ticket.
Inputs: duration (required), ticketId (required), billable, workType, +1 more.
superops_tickets_updateC
Update an existing ticket - change status, priority, assignment, or add resolution.
Inputs: ticketId (required), status, priority, assigneeId, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action. Assets, clients, technicians, and tickets have separate tools for listing, getting, and specific operations (e.g., patches, software, search, groups, notes, time logging). Utility tools like custom_query and navigate serve clear auxiliary purposes without overlapping domain tools.
All tools follow a consistent 'superops_{domain}_{action}' pattern with snake_case. Domains are plural (e.g., assets, clients) and actions describe the operation (list, get, create, etc.). The pattern is uniform across all 21 tools, making it predictable for agents.
21 tools cover multiple domains (assets, clients, technicians, tickets) plus utility tools. While slightly above the 3-15 ideal range, the count is justified by the breadth of functionality needed for a PSA/RMM platform. It is not excessive and each tool has a clear role.
Core workflows for tickets (CRUD, notes, time logging) and assets (list, details, patches, software) are well-covered. Clients and technicians have basic retrieval and listing, but lack create/update/delete tools. The custom mutation/query tools fill advanced gaps, but some standard operations are missing.
Related MCP Connectors
MCP server for interacting with the Supabase platform
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
The official Planning Center MCP server for interacting with your ministry's data.
Related MCP Servers
- AlicenseAqualityBmaintenanceAn MCP server for SuperOps PSA/RMM, enabling MSPs to manage tickets, assets, clients, and field technician operations through SuperOps's API.223Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for interacting with Sophos Central APIs, providing 255 tools for managing endpoints, alerts, policies, and more across partners, organizations, and single tenants.635 npm19MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with the SuperOps.ai PSA/RMM platform for managing clients, tickets, assets, and technicians via GraphQL API.Apache 2.0
- AlicenseBqualityDmaintenanceMCP server for the Level v2 REST API, enabling management of alerts, automations, devices, groups, tags, updates, and custom fields through typed tools.351MIT