Connect SuperOps to Conduit

This walkthrough connects SuperOps (RMM) to Conduit through Conduit’s SuperOps server and a SuperOps API token. Once connected, any MCP client your organization uses can call SuperOps tools through Conduit’s gateway.

SuperOps also hosts its own MCP server. To use that instead, follow SuperOps (First-Party MCP). The two connections are independent; this API-token connection stays available.

SuperOps exposes a GraphQL API; Conduit sends your token as a bearer token and your subdomain alongside it on every call, so both values must belong to the same SuperOps account.

Menu labels can change

The SuperOps-portal steps below stay deliberately generic; menu labels can shift between SuperOps releases. Follow SuperOps’ API integration guide as the authority for creating a token.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A SuperOps account that can create API tokens. The token acts with the permissions of the user it belongs to.
• Your SuperOps subdomain — the first part of the address you sign in at.

Step 1 — Create an API token in SuperOps

1. Sign in to SuperOps.
2. Create an API token following SuperOps’ guide. Expected: an API token value.
3. Copy the token.

Caution

Copy the token now and store it somewhere safe. Don’t paste it into chat, email, or a shared document — the next step moves it directly into Conduit, which encrypts it at rest. If you accidentally expose the token, regenerate it in SuperOps first; the exposed token becomes useless immediately.

Step 2 — Connect SuperOps in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find SuperOps in the catalog (under RMM) and click Connect. Expected: a credential form with two fields.
3. Fill the fields:
   • API Token (required) — from Step 1.
   • Subdomain (required) — just the subdomain of your SuperOps account (e.g. yourcompany), not a full URL. SuperOps requires it on every API call to route requests to your tenant.
4. Click Connect. Expected: Conduit runs a minimal GraphQL query against SuperOps immediately and shows a green Connected status. A bad token or subdomain is rejected here, not on the first tool call.

The credential is stored at the organization scope, so every technician in your org shares this SuperOps connection. (For per-technician tokens, connect at the personal scope instead — see Vendor connections.)

Verify it worked

Connect an MCP client to Conduit — Claude Desktop, Claude Code, Cursor, or any MCP-compatible client (see Connecting an AI client) — and ask it to run a read-only SuperOps tool, such as listing clients or recent tickets. You should get real data back, and the call appears in your audit log with the correct user, vendor (superops), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid SuperOps API token or subdomain.”	The token is wrong or revoked, or the subdomain doesn’t belong to the same account as the token. Verify both — they must match.
Connect fails with “SuperOps returned HTTP <status>.”	SuperOps’ API returned an unexpected error — often a transient SuperOps-side issue. Retry after a moment.
Tool calls return 403 “no credentials for vendor”	SuperOps isn’t connected at a scope this user can resolve. Connect it at the organization scope, or confirm the user’s team has a token.
Tool calls succeed but specific actions are denied	The token acts as the SuperOps user it belongs to. Adjust that user’s role in SuperOps, or create a token under a user with the needed permissions.
Need to rotate the token	Generate a new token in SuperOps, then update the credential at /org/catalog.

Related

• Vendor connections — credential scopes, rotation, and the full vendor catalog.
• Security — how Conduit encrypts and resolves the credential you just stored.
• SuperOps developer documentation — GraphQL API reference.