Skip to main content
MCP (Model Context Protocol) is an open protocol for connecting agents to external tools and data sources. You can add custom MCP servers to Realm to extend your agents’ capabilities beyond built-in tools.
MCP servers are not available on trial plans.

​
Adding a server

1

Open MCP settings

Click Add MCP server on the Tools page. On the MCP servers page, you can either connect one of the Featured MCP servers with one click, or add a custom server under Add a server.
2

Enter server URL

Provide the URL of the MCP server. Use the server’s own documentation when possible. As a rule of thumb, a URL ending in /mcp usually uses Streamable HTTP, while one ending in /sse usually uses Server-Sent Events.
3

Choose transport type

Select Streamable HTTP or Server-Sent Events (SSE) to match the server.
4

Configure authentication

Choose OAuth, Bearer Token, Basic Auth, or Custom Headers and enter the required credentials. Basic Auth takes a username and password, such as a service user ID and its token, and sends them as an HTTP Basic Authorization header. The username can’t contain a colon. You can add headers such as x-api-key or vendor version headers. The Authorization header is managed separately by the authentication type.
5

Name the connection

Optionally give the connection a descriptive name. This is useful when connecting to the same server multiple times with different credentials.
6

Add the server

Click Connect to complete the setup. For OAuth, you first authorize Realm with the provider. Realm then opens the server’s page, which shows the connection status and the server’s tools.
Realm highlights these featured MCP servers for quick one-click setup:

Asana

Atlassian

Intercom

Linear

Notion

Sentry

Stripe

Webflow

​
Managing servers

Once added, you can reconnect or delete MCP servers from the Tools page. Admins can also manage MCP connections created by other admins in the same workspace, including updating connection names, bearer tokens, Basic auth credentials, and custom header values. For OAuth connections, reconnection must be performed by the admin who owns the connection. Other admins can remove the OAuth connection and create a new one with their own credentials if needed. When a connected server’s authorization later fails (for example, an expired OAuth token), its tools become unavailable to the agent. If the agent could have used such a tool during a chat, the assistant message shows a disconnected connector notice naming the affected server, with a Reconnect action for connections you own. For connections owned by another admin, the notice asks you to have the owner reconnect. Realm also notifies you, in the app and by email, the first time a connection fails. The connection’s owner gets a notification with a Reconnect link. For a connection shared with the whole workspace, admins who manage tools are notified too, so a broken connection never silently stops agents and triggers that depend on it. You are not notified again while the connection stays failed. Reconnecting restores it. A connection attempt that never finished, for example because the sign-in window was closed, shows as Not connected with a Connect action for the person who started it. Other admins don’t see unfinished attempts.