Other MCP Servers

Connect Notion, Atlassian, or your own MCP server so the AI Assistant can use that server's tools as you.

Most teams paste exports from Notion, Jira, or a homegrown tool into a chat window, then answer from a copy that is already out of date. In Threaded, the AI Assistant can call a Model Context Protocol (MCP) server you connect, with your sign-in to that server, and use its tools while you work.

Threaded’s own connection is covered in Connecting Threaded MCP. This article is the other servers on the same page.

#What it is

  • MCP Connections. The Admin page that lists the MCP servers the assistant can use for you in this organization.
  • Built-in server. A server Threaded already knows: Threaded MCP, Notion, and Atlassian.
  • Custom server. A server you add by name and HTTPS address. The tile describes it as Custom MCP connector.
  • Your connection. The sign-in is yours. A teammate’s Notion or custom server is a different connection, and a connection in one organization stays in that organization.

#Rules

  • Owners and Editors find MCP Connections under Admin. That menu is where they look, not a permission check: any member of the organization can open the page by its address and connect a server for their own account. A connection is yours, and it applies only in this organization.
  • The AI assistant has to be turned on. On Admin › MCP connections, the empty state is The AI is off: “MCP connections need the AI assistant, which is not turned on for this organization.”
  • Threaded MCP is listed whenever the AI assistant is on. Notion, Atlassian, and Add custom appear when additional MCP servers are turned on for the organization. See Feature Access and Billing.
  • Turning that feature off hides the other servers from this page and from the assistant. The saved sign-in stays on your account and shows again when the feature is on, if the token is still valid.
  • A server is connected only when your token is present, still in date, and readable. An expired token or a token Threaded cannot read is listed as not connected. Sign in again. Threaded waits for you; it does not open that server’s sign-in on its own.
  • The assistant calls the other server with your token, so that server applies your access there. In Ask mode, every call waits for you to approve it, including a read. In Agent mode, the call runs. A server that needs sign-in stops the turn on a Connect card in either mode.
  • A custom server has to be HTTPS, on a public hostname, and it has to support OAuth with automatic client registration (dynamic client registration). A private address, a URL with a username or password in it, or a server with no registration endpoint is refused. A URL with no path is stored with /mcp on the end.
  • Disconnect clears your token for that server. A built-in server stays on the page as Disconnected, with Connect rather than Manage. That is also what you see when a built-in server rejects your sign-in. A custom server leaves the list in both cases.

#In the app

#Open MCP Connections

Owners and Editors open the Admin gear and choose MCP connections. The heading is MCP connections, and the description reads: “Connect MCP servers for AI chat in this organization. Connections stay in this organization. Custom connectors need OAuth with automatic client registration.”

The icon at the top of the AI Assistant sidebar opens the same page. The page summarizes the grid as Checking MCP connections while it loads, then 2 of 3 connected (your counts).

Each tile shows the server name, its address, and one status:

  • Connecting while sign-in is in progress, with Cancel.
  • Connected, with Manage.
  • Expired when the token is past its expiry and you did not disconnect, with Reauthorize.
  • Disconnected when there is no usable token, with Connect. That includes a token Threaded cannot read, as long as it is not also past its expiry.

Manage offers Reauthorize and Disconnect.

#Connect Notion or Atlassian

Click Connect on Notion or Atlassian. A browser window opens for that service’s sign-in. When it finishes, the tile shows Connected. The assistant can then use that server’s tools in this organization.

#Add a custom server

With additional MCP servers turned on, click Add MCP connection.

The dialog title is Add custom MCP connector.

  1. Enter a Display name. Threaded shows Server slug: under that name. The slug is lowercase, starts with a letter, and uses single hyphens. It cannot be threaded, notion, or atlassian.
  2. Enter the MCP server URL, for example https://mcp.example.com/mcp. The hint under the field is: “Search for an MCP for your app that supports OAuth with automatic client registration (DCR today).” A URL with no path is stored with /mcp on the end.
  3. Click Continue to OAuth and finish sign-in in the browser window. There is no field to paste a client id. Threaded registers one when you continue.

The new tile uses your display name. Its description is Custom MCP connector.

#How the assistant uses the tools

Ask in the AI Assistant for something that server can do. The assistant lists that server’s tools and calls the one that fits, using your sign-in.

In Ask mode, the turn waits until you approve the call. In Agent mode, the call runs. Switch modes from the Agent / Ask control in the assistant. The tooltips are Agent mode: tools run without asking and Ask mode: confirm before changing data. For these servers, Ask mode also waits before a read, because the call still sends the request to that server.

If the token is expired or unreadable, the assistant lists the server as needing sign-in and shows a card: “Connect Notion so the assistant can use its MCP tools in this organization.” (The name is the server’s display name.) Connect opens the same sign-in as the tile. Cancel leaves it disconnected. After a successful sign-in the card reads Connected.

#Troubleshooting

The tile says Expired. The token is past its expiry and you did not disconnect. Click Reauthorize and sign in again. Until you do, the page counts the server as not connected, and the assistant asks you to connect it.

A custom server you added is gone from the page. Threaded removes a custom server from this list when its service rejects your sign-in, the same as after Disconnect. Add it again with Add custom and sign in. A built-in server is not removed. It shows as Disconnected, with Connect rather than Manage.

The tile says Disconnected and the assistant still asks you to connect a server you already added. The saved token is missing or Threaded cannot read it, so the inventory reports the server as not connected. Click Connect and sign in again.

Reconnect, with an error on the tile. The last sign-in or session check failed. The error is on the tile. Click Reconnect and complete sign-in again.

Add custom is missing, and only Threaded MCP is listed. Additional MCP servers are off for this organization. See Feature Access and Billing.

The custom server dialog shows an error about automatic client registration. That server has no OAuth registration endpoint. Use a server that supports it, such as Notion, or ask the server’s owner to enable dynamic client registration.

The dialog rejects the URL. Use https://, a public hostname, and no username or password in the address. Addresses that point at a private or reserved network are refused.

A teammate’s server is missing from your page. Connections are per person. They connect their own account on MCP Connections.

#From the CLI or API

There is no dedicated threaded command for these servers. A person signed in to the organization uses threaded api call to list them. Adding a server and finishing sign-in happen in the app. A Threaded API token is refused: Service tokens cannot access this endpoint. The sign-in endpoints also refuse MCP job tokens: Job tokens cannot access this endpoint.

  • organization_mcp_connectors_list: the same inventory as MCP Connections, for the signed-in person. Each entry has connection.connected.
  • Add custom and Connect finish in the app. The API that starts sign-in returns the server’s authorize address without the sign-in parameters, and the browser returns to the app’s /oauth/mcp/callback page, which only completes a sign-in the app started.
  • Disconnect is not a threaded api call operation. The CLI blocks DELETE operations. Disconnect in the app, or send DELETE /api/v1/organizations/<org_uuid>/mcp/connections/<server_slug>/revoke/ as a signed-in person. A 204 clears the token.

Statuses on connection.connected:

  • true: the token is present, in date, and readable. The tile shows Connected, and the assistant can call that server.
  • false, with tokenExpiresAt in the past and revokedAt empty: the tile shows Expired and Reauthorize. The assistant lists the server as needing sign-in.
  • false otherwise: the tile shows Disconnected and Connect. This includes a token Threaded cannot read when the expiry has not passed. The assistant lists that server as needing sign-in too. A custom server you disconnected is omitted from the list.

Common errors:

  • 403 External MCP is not allowed for this organization. Additional MCP servers are off. Threaded MCP still lists.
  • 403 You are not a member of this organization. The call used another organization’s id.
  • 403 Service tokens cannot access this endpoint. Use a person’s sign-in, not a Threaded API token.
  • Disconnect through threaded api call (organization_mcp_connection_destroy) fails before any request is sent. Disconnect in the app, or use the REST DELETE above.
  • 400 redirect_uri is not allowed for hosted MCP OAuth. The address has to be the app’s /oauth/mcp/callback. A redirect of your own is refused when starting or finishing sign-in.
  • 400 This MCP server does not support OAuth with automatic client registration (DCR). Need a registration endpoint (e.g. Notion). Pick a server that supports it.
  • 400 on mcp_origin: MCP server URL must use https. Send an https:// origin.
  • 400 on mcp_origin: MCP server URL must not target private or reserved IP addresses. Use a public hostname.
  • 400 on mcp_origin: MCP server URL must not include credentials. Take the username and password out of the URL.
  • 400 server_slug conflicts with a built-in connector. threaded, notion, and atlassian are reserved. Pick another slug.
  • 400 Invalid or expired MCP OAuth state. Start sign-in again from Connect.
  • 502 Remote MCP token exchange failed. The server rejected the sign-in code. Connect again from the tile.

For example, to list the servers for the signed-in person:

threaded api call --operation-id organization_mcp_connectors_list --path organization_uuid=<org_uuid>

#Why this matters

The assistant can work from the systems your process already lives in, with each person’s own access, and you can disconnect a server the moment you want that access to stop.