SuperOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPEROPS_REGION | No | Region of your SuperOps instance: 'us' or 'eu'. | us |
| SUPEROPS_API_TOKEN | Yes | Your SuperOps.ai API token obtained from My Profile > API token. | |
| SUPEROPS_SUBDOMAIN | Yes | Your company subdomain in SuperOps.ai. |
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 | {} |
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 |
|---|---|
No resources | |
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.