> ## Documentation Index
> Fetch the complete documentation index at: https://test-8862363a-tembo-docs-codex-usage-reset.mintlify.site/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 (Model Context Protocol) servers let agents use external tools and data during sessions.
## Features
* Install MCP servers from the [Integrations page](https://app.tembo.io/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
## Installation
Go to [Integrations](https://app.tembo.io/integrations).
Install any listed MCP integration (for example, Notion or Stripe). Once connected, the server is available in new sessions.
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](/integrations/apify) | Actors for scraping, browser automation, and extraction |
| [Attio](/integrations/attio) | CRM records, lists, and workspace data |
| [Clerk](/integrations/clerk) | Users, organizations, and authentication data |
| [Context7](/integrations/context7) | Library documentation and version-specific examples |
| [Datadog](/integrations/datadog) | Metrics, logs, traces, monitors, and incidents |
| [Fathom](/integrations/fathom) | Meeting recordings, transcripts, and summaries |
| [Granola](/integrations/granola) | Meeting notes, summaries, and insights |
| [Hamster](/integrations/hamster) | Briefs, plans, context, and delivery updates |
| [HubSpot](/integrations/hubspot) | CRM contacts, deals, companies, and pipeline data |
| [Jam](/integrations/jam) | Bug reports, recordings, and reproduction steps |
| [KERNEL](/integrations/kernel) | Cloud browsers and web automation |
| [Mobbin](/integrations/mobbin) | Mobile and web app design patterns |
| [Neon](/integrations/neon) | Postgres projects and databases |
| [Notte](/integrations/notte) | Cloud browser sessions and automation |
| [PlanetScale](/integrations/planetscale) | Database access and management |
| [PostHog](/integrations/posthog) | Analytics, feature flags, experiments, and insights |
| [Pylon](/integrations/pylon) | Customer accounts and support data |
| [Stripe](/integrations/stripe) | Customers, payments, subscriptions, and products |
| [Supermemory](/integrations/supermemory) | Persistent memory and context |
| [Tavily](/integrations/tavily) | Web search, extraction, mapping, and crawling |
| [TinyFish](/integrations/tinyfish) | Web agents for navigation and extraction |
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.
### 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
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**.
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.
Verify API keys, headers, or environment variables. For `http` and `sse` servers, confirm the URL is reachable from your server environment.