> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add a custom MCP connector to Super Magic

> Register your own remote MCP server as a workspace connector so Super Magic can call its tools from any ticket, alongside Thread's built-in connectors.

<Note>
  **Limited-availability beta.** Custom MCP connectors are rolled out per
  workspace. Contact your Thread account team to have the feature turned on
  before you follow this guide.
</Note>

Thread ships a fixed set of Super Magic connectors (Notion, Zapier, Linear,
NinjaOne, and so on). Custom MCP connectors let an admin point Super Magic at
any additional [Model Context Protocol](https://modelcontextprotocol.io) server
that speaks HTTPS and OAuth, so its tools appear next to the built-in
connectors for every member of your workspace.

Use this page if you host or subscribe to an MCP server that Thread hasn't
shipped a first-class integration for and you want Super Magic to call its
tools from Inbox.

## Before you start

* You must be a **Thread Admin** in the workspace.
* Super Magic must already be enabled for the workspace.
* You need the MCP server's **HTTPS base URL**. Plain `http://` URLs, private
  IPs, and internal hostnames are rejected.
* The server must speak OAuth 2.1. Either:
  * support **Dynamic Client Registration** (Thread will register itself), or
  * give you a **static OAuth client ID** (and secret, if the server issues
    one) that you paste in when you add the connector.
* Each workspace can have up to **20** custom MCP connectors.

## Add the connector (admin)

1. In the Thread Admin app, open **Copilot → Super Magic → Settings**.
2. Scroll to the **Connectors** list. Below the Thread-shipped connectors,
   choose **Add custom connector**.
3. In the modal, fill in:
   * **Name** — how the connector will appear to members and to Super Magic
     (for example, `Acme Docs`). Use the real product name so Super Magic
     recognizes it when a member mentions it in chat.
   * **Description** *(optional)* — a short note for other admins about what
     this connector is for.
   * **MCP URL** — the server's HTTPS endpoint (for example,
     `https://mcp.example.com/mcp`).
   * **Client ID** and **Client secret** *(optional)* — leave both blank if the
     server supports Dynamic Client Registration. Fill them in only if your
     server requires a pre-registered OAuth client.
4. Choose **Add**.

Thread probes the URL's OAuth metadata before saving. If discovery fails, the
modal shows an error and no row is created. Fix the URL or client credentials
and try again.

Once saved, the connector is **enabled** for the workspace and shows up in
every member's Connectors list in Inbox.

## Rename, change the URL, or remove a connector

From the same **Super Magic → Settings** screen:

* **Rename or change the URL** — open the connector's row and edit the fields.
  Changing the MCP URL clears any registered OAuth credentials, so every
  member has to reconnect. To rotate a client secret, paste the new value in
  the **Client secret** field; leave it blank to keep the stored one.
* **Remove the connector** — delete the row. Thread removes the catalog entry
  and revokes every member's stored token for it.

Thread-shipped connectors (Notion, Zapier, Linear, and so on) can only be
enabled or disabled from this screen. Editing and deleting only apply to
connectors you added.

## Connect as a member

Each member connects their own account, exactly like a Thread-shipped
connector:

1. In Inbox, open **Connectors** from the Super Magic panel.
2. Find the custom connector by the name your admin gave it.
3. Choose **Connect** and complete the OAuth sign-in on the provider's site.

Super Magic then sees the tools that server exposes to the member's account,
and nothing more.

## Ask Super Magic to use the connector

Once a member is connected, Super Magic loads the connector's tools on demand.
Because the full tool list can be long, mention the connector by name in your
prompt so Super Magic knows to search for its tools. For example:

```text Prompt theme={null}
Use Acme Docs to find the runbook for onboarding a new mailbox and summarize
the first three steps.
```

Any tool call that changes data still goes through Super Magic's **Confirm
action** card before it runs, the same way it does for built-in connectors.

## Security notes

* Thread blocks custom connectors from pointing at private or loopback
  addresses. The URL must be publicly reachable over HTTPS.
* Client secrets are stored encrypted. The admin screen shows only whether a
  secret is set; it never displays the value back.
* Custom-connector tools live inside Super Magic. They are not exposed over
  the [Thread MCP server](/super-magic/thread-mcp-server-developer-guide),
  so an external MCP client won't see them.

## Related

* [Add external tools to Super Magic with connectors](/super-magic/add-external-tools-to-super-magic-with-connectors-super-mcp) — the built-in connectors Thread ships out of the box.
* [Super Magic Admin Guide](/super-magic/super-magic-admin-guide-setup-access-safety) — access, safety, and confirm-action behavior for every connector.


## Related topics

- [Add External Tools to Super Magic with Connectors](/super-magic/add-external-tools-to-super-magic-with-connectors-super-mcp.md)
- [Thread MCP Server: Developer Guide](/super-magic/thread-mcp-server-developer-guide.md)
- [Use Zapier with Super Magic](/super-magic/use-zapier-with-super-magic.md)