Overview
SuperOps MCP connects your AI assistant directly to your SuperOps MSP workspace. Once set up, your AI client can read and update tickets, query assets and alerts, pull billing data, search across clients, and more, all using natural language.
Before you begin
Admin access to your SuperOps account
Relevant plan features enabled: Ticketing, Windows Management, Client Management, and Knowledge Base, as applicable
An MCP-compatible AI client (Claude, ChatGPT, or a custom LLM)
Setting up MCP Connect
Go to Settings > Others > MCP.
Step 1: OAuth client configuration
Application details
Application Name: Enter a name for this integration. This identifies the connection in your SuperOps account.
Redirect URL: Enter the OAuth callback URL for your AI client. For example, if you are connecting Claude, you can enter: https://claude.ai/api/mcp/auth_callback
For other AI clients, enter the appropriate callback URL. Click Add URL to add multiple redirect URLs.
Permission scopes
Set the data access your AI client will have. For each module, choose:
Read only: the AI can retrieve data
Read & Write: the AI can retrieve, create, and update data
Disable: no access
Module | What it covers |
Tickets | Ticket records, conversations, notes, approvals, SLAs, tasks, and worklogs |
Users | Technicians, technician groups, roles, and access levels |
Clients | Client records, sites, contracts, and client users |
Assets | Device details, activity history, alerts, scripts, and patch status |
IT Documentation | Internal IT documents and documentation categories |
Knowledge Base | KB articles, collections, and article feedback |
Accounting | Invoices, quotes, contracts, payment methods, and tax rates |
Service Catalog | Service catalog items, categories, and service offerings |
Integrations & Webhooks | Integration connections and webhook subscriptions |
Permission scopes apply regardless of user role The scopes you configure here govern what the AI client can access, independent of the individual user's role within SuperOps. A read or write permission enabled in MCP Connect applies even if the connected user does not have that access in their SuperOps account. Only configure MCP Connect through admin accounts, or accounts with appropriate access to all modules you intend to enable. |
Step 2: Key and credentials
After saving Step 1, the Key and Credentials page shows three items. Copy each one before leaving this page.
Remote MCP Server URL: your account's MCP endpoint, specific to your data region. You will need it to connect your AI client.
Client ID: copy this for your integration.
Secret Key: the credential your AI client uses alongside the Client ID to authenticate with SuperOps over MCP. Store it securely in your AI client's configuration. It is shown only once and cannot be retrieved after you leave this page. If you lose it, use Rotate Key to generate a new one.
For custom AI agent builders If you are building a custom AI agent, add the following to your MCP configuration file. Use the Remote MCP Server URL from Step 2. Replace "superops-msp" with any name you prefer. { "mcpServers": { "superops-msp": { "command": "npx", "args": [ "mcp-remote", "<remote-mcp-server-url>", "--header", "Authorization:Bearer <your-api-token>", "--header", "X-Customer-Subdomain:<your-subdomain>" ] } } }
• <remote-mcp-server-url>: Remote MCP Server URL from Step 2 • <your-api-token>: your SuperOps API authentication token • <your-subdomain>: your subdomain (for example, acme for acme.superops.com) |
What you can do with SuperOps MCP
SuperOps MCP organizes its tools by module. Your AI client discovers the right tool for each task automatically. Below is a summary of what is available and what your AI client can read or update in each module.
Tickets
Query and manage ticket records, conversations, notes, approvals, SLAs, tasks, and time tracking.
Read
List and filter tickets by status, priority, requester, client, technician, date range, and custom fields
View ticket details, conversation history, internal notes, and SLA status
List tasks, worklogs, and approvals linked to a ticket
Write
Create a new ticket with category, assignment, client, requester, and custom fields
Update status, priority, category, assignment, and custom fields
Add replies and internal notes to a ticket
Delete a ticket (soft-delete, restorable within 30 days) or restore one
Assets
Query and manage device details, software inventory, patch history, activity history, scripts, and alerts.
Read
List and filter assets by status, platform, client, site, and patch status
View asset details, software inventory, disk information, and patch history
View activity history: script runs, patch installs, alerts, and remote sessions
List available scripts and filter alerts by severity, status, and asset
Write
Update an asset's name and assignment
Delete an asset (soft-delete) or restore one
Clients
Query MSP customer records, sites, contracts, and users.
Read
List and filter clients by stage, status, and account manager
View client details, sites, contracts, and users
Billing and financial
Query invoices, quotes, payment methods, and tax configuration.
Read
List and view invoices, quotes, and payment methods
List tax rates and service catalog items
Service catalog
Query service catalog items, categories, and offerings.
Read
List and view catalog items and categories
View offered and eligible service items for clients
Knowledge base
Query KB articles, collections, IT documentation, and article feedback.
Read
List KB articles and collections with status and type filters
View article details and feedback
List IT documentation categories and view individual documents
Admin and configuration
Query technicians, roles, groups, teams, sites, holidays, and company settings.
Read
List technicians, technician groups, and roles
View site details, holiday calendars, and company information
List webhook subscriptions
Custom fields
Look up field definitions and allowed values used in other modules.
Read
Fetch all custom field definitions for any module
Retrieve allowed values and dropdown options for any field
Search
Natural language search across your workspace.
Search across Users, Clients, Tickets, Tasks, and Assets using plain English
Results ranked by relevance with support for filtering by client and site
MODULE availability depends on enabled plan features: CLIENT requires Client Management; TICKET requires Ticketing; ASSET requires Windows Management
Developer tools reference
This section is for teams building custom AI agents on top of SuperOps MCP. When your AI client connects, it sees a compact set of gateway tools rather than the full internal tool catalog. Each gateway uses a two-step search-then-execute pattern.
Note For setup instructions and module capability summaries, see the sections above. |
Tools exposed on connect
Tools appear only when the corresponding module has at least one operation that survives plan, role, and OAuth scope filtering.
Tool | Description |
getCurrentUser | Returns the identity of the signed-in user: userId, name, and email. No arguments required. |
search | Hybrid keyword and semantic search across Users, Clients, Tickets, Tasks, and Assets. |
ticketQueryTool | Gateway for all ticket-related read operations. |
ticketMutationTool | Gateway for all ticket-related write operations. |
assetQueryTool | Gateway for all asset-related read operations. |
assetMutationTool | Gateway for all asset-related write operations. |
clientQueryTool | Gateway for all client-related read operations. MSP only. |
knowledgeQueryTool | Gateway for all knowledge base read operations. |
billingQueryTool | Gateway for all billing and financial read operations. MSP only. |
adminQueryTool | Gateway for all admin and configuration read operations. |
fieldsQueryTool | Gateway for all custom field read operations. |
How gateway tools work
Each gateway is a two-step proxy.
Step 1: action="search" — pass a plain-English query to return the best-matching tools in that module, each with its name, description, and input schema.
Step 2: action="execute" — pass the exact tool name from Step 1 and the required arguments to run the operation.
What each gateway contains
ticketQueryTool
Tool | Description |
getTicketList | Lists tickets with filtering, sorting, and pagination. |
getTicketConversationsList | Lists conversation entries for a ticket, including replies and notifications. |
getTicket | Fetches a ticket. |
getTaskList | Fetches a list of tasks. |
getTask | Fetches a task. |
getWorklogList | Fetches a list of worklogs. |
getWorklog | Fetches a worklog. |
getSLAList | Fetches a list of SLA records associated with a ticket. |
getApprovals | Fetches the list of approvals for a ticket. |
ticketMutationTool
Tool | Description |
createTicket | Creates a new ticket. |
updateTicket | Updates an existing ticket's fields, assignment, and custom data. |
deleteTicket | Soft-deletes a ticket. Restorable within 30 days. |
restoreTicket | Restores a soft-deleted ticket. |
createTicketConversation | Adds a reply or notification to a ticket's conversation. |
createNote | Adds an internal note to a ticket. |
updateNote | Updates an existing internal note on a ticket. |
assetQueryTool
Tool | Description |
getAssetList | Lists assets with filtering, sorting, and pagination. |
getAssetActivity | Retrieves detailed activity history for an asset. |
getAlertList | Lists alerts with filtering by severity, status, and asset. |
getAsset | Fetches an asset. |
getAssetSummary | Fetches the asset's summary details. |
getAssetPatchDetails | Fetches all patch details for an asset. |
getScriptList | Fetches all available scripts. |
assetMutationTool
Tool | Description |
updateAsset | Updates an asset's name, dates, and assignment details. |
deleteAsset | Soft-deletes an asset. |
restoreAsset | Restores a soft-deleted asset. |
clientQueryTool (MSP only)
Tool | Description |
getClientList | Lists clients with filtering and pagination. MSP only. |
getClient | Fetches a client. |
getClientSiteList | Fetches a list of client sites. |
getClientSite | Fetches a client site. |
getClientContractList | Fetches a list of client contracts. |
getClientContract | Fetches a client contract. |
getClientUserList | Fetches a list of client users. |
getClientUser | Fetches a client user. |
getClientStageList | Fetches a list of client stages. |
knowledgeQueryTool
Tool | Description |
getKbItems | Lists KB items (articles and collections) with filtering and pagination. |
getKbItem | Fetches the details of a specific KB item. |
getItDocumentationList | Fetches all IT documents under a category. |
getItDocumentation | Fetches an IT document's details. |
getKbArticleFeedbacks | Fetches feedback entries submitted for KB articles. |
billingQueryTool (MSP only)
Tool | Description |
getInvoiceList | Fetches a list of invoices. |
getInvoice | Fetches an invoice. |
getQuoteList | Fetches a list of quotes. |
getQuote | Fetches a quote. |
getServiceCatalogItemList | Retrieves a list of all products and services. |
getServiceCatalogItem | Retrieves a product or service. |
getPaymentMethodList | Fetches the list of payment methods. |
getTaxList | Fetches all tax rates. |
adminQueryTool
Tool | Description |
getTechnicianList | Fetches the list of technicians. |
getUserList | Fetches a list of users. |
getUser | Fetches a user by ID. |
getSiteList | Fetches a list of sites. |
getDepartmentList | Fetches a list of departments. |
getHolidayList | Fetches the list of holiday lists. |
getWebhookSubscriptionList | Fetches a list of webhook subscriptions. |
getCompanyInfo | Fetches company information and settings. |
fieldsQueryTool
Tool | Description |
getAllFields | Fetches all fields for a specified module. |
getField | Fetches a field by module. |
getFields | Fetches fields by module. |
getOptions | Fetches the options for a field. |