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

# MCP

> Connect custom MCP servers to extend what your agents can do

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.

<Note>MCP servers are not available on trial plans.</Note>

## Adding a server

<Steps>
  <Step title="Open MCP settings">
    Click **Add MCP Server** from the Tools page. You can either connect a **Featured MCP Server** with one click, or add a custom server manually.

    <Frame caption="Add MCP Server button">
      <img src="https://mintcdn.com/realm/Qm6Eir5Q8Rj5_NIa/images/admin/tools-add-mcp-server.png?fit=max&auto=format&n=Qm6Eir5Q8Rj5_NIa&q=85&s=25c1c6d0915ddd2e1f305f3feac36001" alt="Add MCP Server button" width="1508" height="300" data-path="images/admin/tools-add-mcp-server.png" />
    </Frame>

    <Frame caption="Featured MCP Servers">
      <img src="https://mintcdn.com/realm/Qm6Eir5Q8Rj5_NIa/images/admin/tools-featured-mcp.png?fit=max&auto=format&n=Qm6Eir5Q8Rj5_NIa&q=85&s=55a2e56ba48d180ccf6c20819c05a231" alt="Featured MCP Servers" width="1470" height="457" data-path="images/admin/tools-featured-mcp.png" />
    </Frame>
  </Step>

  <Step title="Enter server URL">
    Provide the URL of the MCP server.
  </Step>

  <Step title="Choose transport type">
    Select **HTTP** or **SSE** (Server-Sent Events).
  </Step>

  <Step title="Configure authentication">
    Choose **OAuth** or **Bearer Token** and enter the required credentials. You can also add **custom headers** (e.g. `x-api-key` or vendor version headers). The `Authorization` header is managed separately by the authentication type.
  </Step>

  <Step title="Name the connection">
    Optionally give the connection a descriptive name. This is useful when connecting to the same server multiple times with different credentials.
  </Step>

  <Step title="Add the server">
    Click **Connect** to complete the setup.

    <Frame caption="Add MCP Server form">
      <img src="https://mintcdn.com/realm/Qm6Eir5Q8Rj5_NIa/images/admin/tools-add-mcp-form.png?fit=max&auto=format&n=Qm6Eir5Q8Rj5_NIa&q=85&s=addc4aaf9f59236015428bc419383c3f" alt="Add MCP Server form" width="1506" height="1080" data-path="images/admin/tools-add-mcp-form.png" />
    </Frame>
  </Step>
</Steps>

## Featured servers

Realm highlights these featured MCP servers for quick one-click setup:

<CardGroup cols={3}>
  <Card title="Asana" icon="server" />

  <Card title="Atlassian" icon="confluence" />

  <Card title="Intercom" icon="intercom" />

  <Card title="Linear" icon="diagram-project" />

  <Card title="Notion" icon="n" />

  <Card title="Sentry" icon="bug" />

  <Card title="Stripe" icon="stripe" />

  <Card title="Webflow" icon="server" />
</CardGroup>

## 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, 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.