superops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPEROPS_REGION | No | Region: 'us' or 'eu' | us |
| SUPEROPS_API_TOKEN | Yes | Your SuperOps.ai API token | |
| SUPEROPS_SUBDOMAIN | Yes | Your company subdomain |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| superops_navigateA | Discover available SuperOps.ai tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite. |
| superops_statusB | Show credentials status and available domains |
| superops_test_connectionA | Test the connection to SuperOps.ai API using configured credentials. |
| superops_clients_listA | List clients (accounts) in SuperOps.ai. Can filter by status, stage, or paginate through results. |
| superops_clients_getA | Get detailed information for a specific client by their account ID. |
| superops_clients_searchA | Search for clients by name or email domain. Returns matching clients with basic information. |
| superops_tickets_listB | List tickets in SuperOps.ai. Can filter by status, priority, client, or assignee. |
| superops_tickets_getA | Get detailed information for a specific ticket by its ID. |
| superops_tickets_createC | Create a new ticket in SuperOps.ai. |
| superops_tickets_updateC | Update an existing ticket - change status, priority, assignment, or add resolution. |
| superops_tickets_add_noteA | Add a note to a ticket. Can be internal or public (visible to client). |
| superops_tickets_log_timeB | Log time spent on a ticket. |
| superops_assets_listA | List assets (endpoints) in SuperOps.ai RMM. Can filter by status, platform, or client. |
| superops_assets_getA | Get detailed information for a specific asset including hardware, OS, and network details. |
| superops_assets_softwareA | Get the software inventory for a specific asset. |
| superops_assets_patchesA | Get patch status and pending patches for a specific asset. |
| superops_technicians_listB | List technicians (agents) in SuperOps.ai. Can filter by active status or team. |
| superops_technicians_getA | Get detailed information for a specific technician by their ID. |
| superops_technicians_groupsB | List technician groups/teams in SuperOps.ai. |
| superops_custom_queryA | Run a custom GraphQL query against the SuperOps.ai API. For advanced use cases not covered by standard tools. |
| superops_custom_mutationB | Run a custom GraphQL mutation against the SuperOps.ai API. For advanced write operations not covered by standard tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SuperOps Ticket Card | Interactive MCP Apps card rendering a SuperOps.ai ticket |
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action (clients, tickets, assets, technicians). The utility tools (navigate, status, test_connection) have clearly separate purposes, and list vs search or get vs list are unambiguous with the given descriptions.
The naming follows a consistent superops_<resource>_<operation> pattern for most tools, but some operations are nouns (software, patches, groups) rather than verbs, and utility tools (navigate, status, test_connection) don't follow the resource pattern. Still, the overall style is uniform and predictable.
21 tools is on the higher end but justified given the multi-domain coverage (clients, tickets, assets, technicians) plus utility and custom GraphQL tools. It covers a broad platform without being excessive.
The ticket lifecycle is well covered (create, update, add note, log time), and read operations exist for all main entities. Gaps include no client creation/update and no asset actions, but the custom query/mutation tools provide a fallback for advanced operations.