PSA integration · Beta
Evaluate the SuperOps MCP server for your MSP stack.
The Stackyapper SuperOps connection is available for evaluation. Beta apps may change and should begin with a small set of read-only tools.
What is the Stackyapper SuperOps MCP integration?
The Stackyapper SuperOps integration lets compatible AI clients use approved SuperOps tools without receiving the provider credential.
What can the SuperOps integration do?
MSP PSA/RMM visibility — clients, tickets, assets, and alerts through the regional SuperOps GraphQL API. Each technician uses their own API token.
Available tools depend on the provider account, workspace settings, and the signed-in user’s permissions.
Who is the SuperOps MCP integration for?
It is for SuperOps-based MSPs evaluating AI access to selected PSA and RMM details under each technician’s own provider token.
What is the current support status?
| Status | Beta |
|---|---|
| App review | In review |
| What that means | Available for evaluation, may change, and should begin with read-only tools. |
| Catalog category | PSA |
| Catalog audience | msp |
| Credential handling | Each technician supplies their SuperOps region, customer subdomain, and personal API token. |
| Customer access | MSP workspace only |
Start in a test workspace with one read-only tool and a request for no more than five records.
What can an MSP use it for?
- Evaluate approved client and ticket context.
- Review permitted asset and alert information during triage.
- Test technician-scoped access against the correct region.
Exact tools depend on provider authorization, credential ownership, workspace settings, and the signed-in user’s permissions.
What should I expect?
| Provider scope | MSP PSA/RMM visibility — clients, tickets, assets, and alerts through the regional SuperOps GraphQL API. Each technician uses their own API token. |
|---|---|
| Available tools | Compatible clients see only the tools available to the signed-in user in the selected workspace. |
| Write actions | If a write tool is available, Stackyapper applies its permissions and confirmation requirements before it runs. |
| API coverage | This page lists the capabilities Stackyapper currently supports, not every endpoint in the provider API. |
How is SuperOps access controlled?
- An administrator configures SuperOps for the intended Stackyapper workspace, and each authorized user connects their own provider identity or credential.
- The administrator grants available tools to specific workspaces, groups, or people.
- Stackyapper resolves the connection within the current credential and tenant scope.
- Stackyapper checks permissions and safety controls again before every request.
- Actions that require confirmation do not execute until the exact request is confirmed.
Does SuperOps send its API credential to Claude or ChatGPT?
No. Stackyapper keeps the encrypted provider credential secure and does not send it to the AI client.
How do I evaluate the SuperOps beta?
- Create or select a non-production Stackyapper workspace.
- Find SuperOps in the app catalog and request beta access if it is not enabled.
- Use the provider authorization described above with the narrowest practical permissions.
- Grant only the read-only tool needed for the evaluation.
- Request no more than five records, confirm the result in Audit, and expand access only when the test succeeds.
Support boundaries
- Stackyapper does not claim that every endpoint in the SuperOps API is exposed.
- Provider plan, account configuration, API scopes, and upstream availability can limit results.
- Administrators are responsible for correct provider permissions and user grants.
- Support status and available tools can change as provider capabilities evolve.
SuperOps MCP questions
Is there a SuperOps MCP server?
Stackyapper has a beta SuperOps MCP connection available for evaluation. Beta apps may change and should begin with a small set of read-only tools.
Can I connect SuperOps to Claude or ChatGPT?
Stackyapper has a beta SuperOps connection for compatible MCP clients. It is available for evaluation and may change. Exact access depends on provider authorization and Stackyapper workspace permissions.
Does Stackyapper expose every SuperOps API endpoint?
No. This page lists the SuperOps capabilities Stackyapper currently supports.
Does SuperOps send its credential to the AI client?
No. Stackyapper keeps the encrypted SuperOps credential secure and does not send it to the AI client.
Related Stackyapper resources
- How the Stackyapper MCP server works for MSPs
- MCP security, credential, and access-control model
- Connect ChatGPT, Claude, Claude Code, or Codex to Stackyapper
- Complete Stackyapper app catalog
- Atera MCP access (beta)
- Syncro MCP access (beta)
- Gorelo MCP access (beta)
Stackyapper is an independent product. Provider availability and API capabilities can change.