Skip to main content

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
MCP (Model Context Protocol) servers let agents use external tools and data during sessions.

Features

  • Install MCP servers from the Integrations page
  • 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)

Installation

1

Open 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.

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.
{
  "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.
{
  "mcpServers": {
    "events-server": {
      "type": "sse",
      "url": "https://example.com/sse"
    }
  }
}

Stdio

Use this when the MCP server runs as a local command.
{
  "mcpServers": {
    "github-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_TOKEN": "ghp_xxx"
      }
    }
  }
}

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
{
  "mcpServers": [
    {
      "name": "api-server",
      "type": "http",
      "url": "https://example.com/mcp"
    }
  ]
}

Advanced

If a remote server requires OAuth, Tembo prompts you to authorize during setup and completes the connection after you approve access.
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.