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

# MCP

> Connect built-in and custom MCP servers for agent tool access.

![MCP](https://mintcdn.com/test-8862363a/_KF7n4fDwDrxMgZe/images/integrations/mcp.png?fit=max\&auto=format\&n=_KF7n4fDwDrxMgZe\&q=85\&s=b3652c9ed6aac788dd45264a36f1fe43)

MCP (Model Context Protocol) servers let agents use external tools and data during sessions.

To connect an external MCP client to the Tembo API, see the [Tembo MCP server](https://docs.tembo.io/api.md#mcp-server).

## Features

* Install MCP servers from **Settings > Integrations**
* Add your own MCP servers with `stdio`, `http`, or `sse` transport
* Connect OAuth-based remote MCP servers
* Enable MCP servers from existing integrations automatically (GitHub, Linear, Sentry, Postgres)
* Scope a custom MCP server to yourself or share it with your workspace
* Reach private MCP servers on your tailnet through the [Tailscale integration](https://docs.tembo.io/integrations/tailscale.md)

## Installation

**1. Open Integrations**

Go to **Settings > Integrations**.

**2. Use built-in MCP servers**

Install any listed MCP integration (for example, Notion or Stripe). Once connected, the server is available in new sessions.

**3. Add a custom server**

Click **Custom MCP**, paste your JSON config, then save.

## Built-in MCP integrations

Use these guides to connect the remote MCP services available in Tembo's catalog. These connections provide tools during sessions; they do not by themselves configure event-triggered agents.

| Integration | Tools and data |
| - | - |
| [Apify](https://docs.tembo.io/integrations/apify.md) | Actors for scraping, browser automation, and extraction |
| [Attio](https://docs.tembo.io/integrations/attio.md) | CRM records, lists, and workspace data |
| [Clerk](https://docs.tembo.io/integrations/clerk.md) | Users, organizations, and authentication data |
| [Cloudflare](https://docs.tembo.io/integrations/cloudflare.md) | Workers, DNS, R2, D1, KV, and the full Cloudflare API |
| [Context.dev](https://docs.tembo.io/integrations/context-dev.md) | Web search, scraping, crawling, and brand data |
| [Context7](https://docs.tembo.io/integrations/context7.md) | Library documentation and version-specific examples |
| [Datadog](https://docs.tembo.io/integrations/datadog.md) | Metrics, logs, traces, monitors, and incidents |
| [Fathom](https://docs.tembo.io/integrations/fathom.md) | Meeting recordings, transcripts, and summaries |
| [Google Docs](https://docs.tembo.io/integrations/google-docs.md) | Google Docs documents |
| [Google Drive](https://docs.tembo.io/integrations/google-drive.md) | Google Drive files |
| [Google Sheets](https://docs.tembo.io/integrations/google-sheets.md) | Spreadsheet values and formulas |
| [Granola](https://docs.tembo.io/integrations/granola.md) | Meeting notes, summaries, and insights |
| [Hamster](https://docs.tembo.io/integrations/hamster.md) | Briefs, plans, context, and delivery updates |
| [HubSpot](https://docs.tembo.io/integrations/hubspot.md) | CRM contacts, deals, companies, and pipeline data |
| [incident.io](https://docs.tembo.io/integrations/incident-io.md) | Incidents, alerts, on-call schedules, and follow-ups |
| [Jam](https://docs.tembo.io/integrations/jam.md) | Bug reports, recordings, and reproduction steps |
| [KERNEL](https://docs.tembo.io/integrations/kernel.md) | Cloud browsers and web automation |
| [Mobbin](https://docs.tembo.io/integrations/mobbin.md) | Mobile and web app design patterns |
| [Neon](https://docs.tembo.io/integrations/neon.md) | Postgres projects and databases |
| [Notte](https://docs.tembo.io/integrations/notte.md) | Cloud browser sessions and automation |
| [Paper](https://docs.tembo.io/integrations/paper.md) | Design files, layouts, and design-to-code |
| [Photon](https://docs.tembo.io/integrations/photon.md) | Projects, messaging channels, messages, and billing usage |
| [PlanetScale](https://docs.tembo.io/integrations/planetscale.md) | Database access and management |
| [PostHog](https://docs.tembo.io/integrations/posthog.md) | Analytics, feature flags, experiments, and insights |
| [Pylon](https://docs.tembo.io/integrations/pylon.md) | Customer accounts and support data |
| [Railway](https://docs.tembo.io/integrations/railway.md) | Projects, service deployments, and environments |
| [Sazabi](https://docs.tembo.io/integrations/sazabi.md) | Production logs, issues, and root-cause investigations |
| [Stripe](https://docs.tembo.io/integrations/stripe.md) | Customers, payments, subscriptions, and products |
| [Supabase](https://docs.tembo.io/integrations/supabase.md) | Supabase projects and databases |
| [Supermemory](https://docs.tembo.io/integrations/supermemory.md) | Persistent memory and context |
| [Tavily](https://docs.tembo.io/integrations/tavily.md) | Web search, extraction, mapping, and crawling |
| [TinyFish](https://docs.tembo.io/integrations/tinyfish.md) | Web agents for navigation and extraction |
| [Vercel](https://docs.tembo.io/integrations/vercel.md) | Projects, deployments, build logs, and documentation |

Review the selected provider account and requested permissions before connecting. Remote MCP tools send requests to the provider's service, even when Tembo is self-hosted. Your installed release and organization settings can affect catalog availability.

## Usage

### Prerequisites

* You have access to your organization in Tembo
* You have the server URL or command needed to start your MCP server
* You have any required credentials (API key, OAuth app, or environment variables)

### Custom server transport types

#### HTTP

Use this for hosted MCP endpoints.

```json theme={null}
{
  "mcpServers": {
    "api-server": {
      "type": "http",
      "url": "https://example.com/mcp",
      "headers": {
        "Authorization": "Bearer token"
      }
    }
  }
}
```

#### SSE

Use this for hosted MCP servers that expose an SSE endpoint.

```json theme={null}
{
  "mcpServers": {
    "events-server": {
      "type": "sse",
      "url": "https://example.com/sse"
    }
  }
}
```

#### Stdio

Use this when the MCP server runs as a local command.

```json theme={null}
{
  "mcpServers": {
    "github-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_TOKEN": "your-github-token"
      }
    }
  }
}
```

### Personal and shared custom servers

When adding a custom server, workspace admins can check **Personal MCP** to make the server available only in sessions they create. Leave it unchecked to share the server with the rest of the workspace. Non-admins always create personal custom servers, and this cannot be changed after the server is created.

### Private servers on your tailnet

If an `http` or `sse` MCP server is only reachable on your [Tailscale](https://tailscale.com) network, sessions can connect to it through the [Tailscale integration](https://docs.tembo.io/integrations/tailscale.md). You don't need to expose it to the public internet.

Before you start:

* Install and enable the [Tailscale integration](https://docs.tembo.io/integrations/tailscale.md)
* Allow your session tag to reach the server's host and port in your tailnet policy. For example, with sessions tagged `tag:tembo-session` and the server tagged `tag:mcp`:

```jsonc theme={null}
"acls": [
  {
    "action": "accept",
    "src":    ["tag:tembo-session"],
    "dst":    ["tag:mcp:443"],
  },
],
```

**1. Add a custom remote server**

Go to **Settings > Integrations**, click **Install** on the **Custom MCP** card, and choose the **Remote** connection type.

![Integrations settings with Tailscale installed and the Custom MCP card's Install button](https://mintcdn.com/test-8862363a/umtnYSJKYfrhmEAk/images/mcp/custom-mcp-card.png?fit=max\&auto=format\&n=umtnYSJKYfrhmEAk\&q=85\&s=ed48638b2d6a3da653ad85b1ca66fc48)

**2. Enter the tailnet URL**

Enter a name and the server's URL on your tailnet. MagicDNS names work, for example `https://mcp.your-tailnet.ts.net/mcp`.

**3. Turn on Reach via Tailscale**

Turn on **Reach via Tailscale**. The toggle is disabled until the Tailscale integration is installed.

**4. Add headers if needed**

Your tailnet ACLs control which sessions can reach the server. If the server also expects a token, add it as a header (for example `Authorization`). OAuth and client credentials aren't available for tailnet servers.

![Add an MCP dialog with a tailnet server URL, Reach via Tailscale turned on, and an Authorization header](https://mintcdn.com/test-8862363a/umtnYSJKYfrhmEAk/images/mcp/reach-via-tailscale.png?fit=max\&auto=format\&n=umtnYSJKYfrhmEAk\&q=85\&s=bacff9148271d3354955223bd48a4e76)

Click **Add MCP** to save the server.

When a session connects to the server, it first joins your tailnet with a single-use, ephemeral key, then sends only that server's requests through the tailnet. Public MCP servers in the same session are unaffected.

Tembo's API never contacts tailnet servers. That means:

* The server shows as connected as soon as you add it, without a connection check. Start a session to confirm Tembo can reach it.
* Connection testing isn't available for tailnet servers.
* You can only turn on **Reach via Tailscale** when you add a server. To switch an existing server, remove it and add it again.

### Configuration formats

Tembo accepts both of these formats:

* Object format (recommended): `mcpServers` is an object keyed by server name
* Array format: `mcpServers` is an array with explicit `name` values

```json theme={null}
{
  "mcpServers": [
    {
      "name": "api-server",
      "type": "http",
      "url": "https://example.com/mcp"
    }
  ]
}
```

## Advanced

> [accordion] OAuth-based servers
>
> If a remote server requires OAuth, choose how the OAuth client is registered when adding the custom server:
>
> * **Automatic**: Tembo registers an OAuth client with servers that support dynamic client registration, then prompts you to authorize during setup and completes the connection after you approve access.
> * **Pre-registered**: Use credentials from an OAuth client you already registered with the MCP provider. Register the callback URL shown in the dialog as the provider's OAuth redirect URL, then enter the **Client ID** (required), **Client Secret** (optional for public clients, but required by some providers such as Slack), and an optional space-separated **Scope**.

> [accordion] Server not showing up in sessions
>
> Check that the JSON is valid, required fields are present, and the integration is saved successfully. Start a new session after saving to pick up updated MCP config.

> [accordion] Authentication or connection errors
>
> Verify API keys, headers, or environment variables. For `http` and `sse` servers, confirm the URL is reachable from your server environment.
>
> For tailnet servers, confirm the Tailscale integration is still enabled and that your ACLs allow your session tag to reach the server's host and port. Connections that time out usually mean the ACL policy doesn't allow the traffic.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.