Skip to content
ConduitConduit

Connect SuperOps first-party MCP to Conduit

This walkthrough connects SuperOps’ own hosted MCP server to Conduit. An admin creates an OAuth client in SuperOps, registers Conduit’s redirect URL, and pastes the Remote MCP Server URL, Client ID, and Secret Key into Conduit. After that, any MCP client your organization uses can call SuperOps through Conduit.

This is separate from the SuperOps API-token connection. That one talks to SuperOps’ GraphQL API through a Conduit-hosted server. This one talks to the MCP server SuperOps hosts. You can keep both.

Before you start

Section titled “Before you start”

You need:

  • A Conduit role that can manage connections — owner or admin on your organization.
  • SuperOps admin access. The scopes you set on the MCP client apply even when the signed-in user’s own SuperOps role is narrower. Only create this client from an admin account.
  • The plan features you want the assistant to use (Ticketing, Windows Management, Client Management, Knowledge Base), as applicable.

Redirect URL to register

Section titled “Redirect URL to register”

In SuperOps, the OAuth client asks for one or more redirect URLs. Register the callback for the Conduit environment you are connecting:

Environment Redirect URL
Production https://conduit.wyre.ai/connect/oauth/callback
Staging https://staging.conduit.wyre.ai/connect/oauth/callback

The connect form also shows the exact URL for the environment you are on. Paste that value. SuperOps will reject the sign-in step if the URL does not match.

There is no WYRE-wide SuperOps OAuth app to install, and no Conduit secret to set. SuperOps creates the Client ID and Secret Key inside your tenant. SUPEROPS_OFFICIAL_CLIENT_ID exists only as an unused placeholder in Conduit’s vendor config — do not provision it.

Step 1 — Create the OAuth client in SuperOps

Section titled “Step 1 — Create the OAuth client in SuperOps”
  1. Sign in to SuperOps as an admin.
  2. Go to Settings → Others → MCP.
  3. Set the application name (anything that identifies Conduit).
  4. Add the redirect URL from the table above.
  5. For each module, choose Read only, Read & Write, or Disable. These scopes are the permission boundary for the connection.
  6. Save. On the next page, copy all three values before you leave:
    • Remote MCP Server URL — specific to your data region.
    • Client ID
    • Secret Key — shown once. If you lose it, use Rotate Key.

Also note your subdomain: the first label of the address you sign in at (acme for acme.superops.com).

Step 2 — Connect in Conduit

Section titled “Step 2 — Connect in Conduit”
  1. In Conduit, go to Connections (/org/catalog).
  2. Find SuperOps (First-Party MCP) under Remote Monitoring & Management and click Connect.
  3. Fill the fields:
    • Remote MCP Server URL — from Step 1, unchanged.
    • OAuth Client ID and Secret Key — from Step 1.
    • Subdomain — the single label, not a full URL.
  4. Click Continue to SuperOps. Sign in and approve access.

Conduit stores the tokens, the client credentials (so it can refresh), the MCP URL, and the subdomain. Later calls go to that MCP URL with Authorization: Bearer and X-Customer-Subdomain.

What the assistant can call

Section titled “What the assistant can call”

SuperOps exposes a small set of gateway tools, not one tool per API operation. A gateway answers in two steps: action search (which operations exist) and action execute (run one of them). Which gateways appear depends on the modules you enabled and your plan.

Conduit classifies those gateways as follows:

Tool Who can call it
getCurrentUser, search, ticketQueryTool, assetQueryTool, knowledgeQueryTool, fieldsQueryTool, catalogQueryTool Read
ticketMutationTool, assetMutationTool Write
adminQueryTool Admin — it returns roles and access levels together with sites and company info

Troubleshooting

Section titled “Troubleshooting”
Symptom Likely cause
SuperOps says the redirect URL is not allowed The URL registered in MCP Connect does not match this Conduit environment. Copy it from the connect form.
Connect form: the URL must be on a SuperOps host The Remote MCP Server URL was edited, or it is not an https:// address on *.superops.ai, *.superops.com, *.superopsmsp.com, or *.mysuperops.com. Paste the value SuperOps showed.
Connect form: couldn’t discover the OAuth settings That URL did not publish OAuth metadata. Confirm MCP Connect is saved and you pasted the Remote MCP Server URL, not the GraphQL API URL (api.superops.ai).
Tool calls return 403 “no credentials for vendor” The first-party connection is not stored at a scope this user can use. Connect it at the organization scope.
A module’s tools never appear That module is Disabled on the OAuth client, or the plan feature is off.
Section titled “Related”