Skip to main content
Availability: AI Pro plan.
Custom connectors work in Super Magic chat only for now. Support in Agent Builder is coming soon.
Thread ships a set of Super Magic connectors (Notion, Zapier, Linear, NinjaOne and others). A custom connector covers the rest: point Super Magic at any remote Model Context Protocol server, and its tools appear next to the built-in ones, so technicians can work in that tool from any ticket without leaving Inbox. Use a custom connector when a vendor you already use publishes an MCP server (your RMM, security stack, documentation platform or PSA add-on) and Thread hasn’t shipped a connector for it.

Choose how the connector signs in

You pick the authentication type when you add the connector, and you can’t change it afterward.
An API key connector gives everyone in the workspace who can use Super Magic the key’s full access. Create a key with the narrowest access the vendor allows, ideally read-only, before you add it.

Before you start

  • You’re a workspace admin in Thread.
  • Your workspace is on the AI Pro plan, and Super Magic is turned on.
  • You have the MCP server’s HTTPS URL, for example https://mcp.example.com/mcp. Plain http:// URLs, private IP addresses and internal hostnames are rejected.
  • For OAuth, the server supports OAuth 2.1. Either it supports dynamic client registration (Thread registers itself), or the vendor gives you a client ID, and a client secret if they issue one.
  • For API key, you have the key and the name of the header the server expects it in, usually Authorization (with a value such as Bearer <key>) or X-API-Key. The vendor’s MCP setup guide lists both.
  • Each workspace can have up to 20 custom connectors.

Add the connector

  1. In Thread Admin, open Magic Agents → Super Magic → Settings.
  2. In the External Tools card, select Add custom connector.
  3. Fill in:
    • Name: how the connector appears to members and to Super Magic. Use the product’s real name, for example Meraki, so Super Magic recognizes it when a technician mentions it.
    • Description (optional): a note for other admins about what the connector is for.
    • MCP URL: the server’s HTTPS endpoint.
  4. Under Authentication, pick one:
    • OAuth (each member signs in): leave Client ID and Client secret blank if the server supports dynamic client registration. Fill them in only if the vendor gave you a client.
    • API key (shared by the workspace): enter the Header name (letters, numbers and dashes) and the Header value, which is the key exactly as the server expects it, including any Bearer prefix.
  5. Select Add.
Add custom connector dialog with Name, Description and MCP URL filled in, Authentication set to OAuth (each member signs in), and optional Client ID and Client secret fields

OAuth: leave Client ID and Client secret blank if the server supports dynamic client registration.

Add custom connector dialog with Authentication set to API key (shared by the workspace), a Header name of X-API-Key, a masked Header value, and a warning about the key's shared access

API key: enter the header name and the key. The dialog reminds you that everyone who can use Super Magic gets the key's access.

Thread checks the server before it saves anything. For OAuth, it reads the server’s sign-in details. For an API key, it connects with your key and lists the server’s tools. If the check fails, the form shows the error and nothing is saved. Fix the URL, key or client details and try again. Once saved, the connector is on for the workspace.
External Tools card in Super Magic settings with the Add custom connector link, built-in integrations, and a custom connector named Acme NetWatch switched On

The new connector in the External Tools card, turned on for the workspace.

Connect your account (OAuth connectors only)

Each member connects their own account once:
  1. In Inbox, open Connectors from the Super Magic panel.
  2. Find the connector by the name your admin gave it.
  3. Select Connect and sign in on the vendor’s site.
Connectors page in Inbox listing connectors with Connected badges and Connect buttons

Connectors in Inbox: each member connects the OAuth connectors their workspace has enabled.

API key connectors don’t appear in the member Connectors list. Their tools are already available in Super Magic.

Use it in Super Magic

Mention the connector by name in your request so Super Magic knows to load its tools:
Prompt
Prompt

Edit or remove a connector

From the same External Tools card in Super Magic settings:
  • Rename it or change the URL: open the connector and edit the fields. For an OAuth connector, changing the URL clears the stored sign-in details, so every member connects again.
  • Rotate a secret or key: paste the new client secret or header value. Leave the field blank to keep the stored one. A new API key takes effect on the next request.
  • Change the authentication type: remove the connector and add it again.
  • Remove it: delete the connector. Thread removes it for everyone and deletes the stored sign-ins and key.

Troubleshooting

  • A connector stops working. A failing connector only takes its own tools offline; Super Magic keeps working with everything else. For an API key connector, the key was usually rotated or revoked at the vendor: paste a new one. For an OAuth connector, connect again from Connectors in Inbox.
  • Super Magic doesn’t use the connector. Name it in your request, using the name shown in Connectors.
  • The connector won’t save. The URL must be public HTTPS and must answer as an MCP server. For an API key, confirm the header name and that the value includes any prefix the vendor requires, such as Bearer .

Security notes

  • Client secrets and API keys are stored encrypted. Thread never shows them again after you save, only whether one is set.
  • Custom connectors can’t point at private or loopback addresses.
  • Custom connector tools work in Super Magic chat only. They aren’t available in Agent Builder yet. They aren’t exposed through the Thread MCP server, so AI apps connected to Thread don’t see them.