MCP

Give your agents access to external tools and data sources.

MCP (Model Context Protocol) servers extend what your agents can access during tasks. Install them from the Integrations page.

Available servers

Server	What it does
Kernel	Chromium browsers, Playwright automation, video replays
Context7	Version-specific documentation and code examples
PostHog	Analytics, feature flags, error tracking
Neon	Neon Postgres databases
Supabase	Supabase projects and databases
PlanetScale	PlanetScale databases
Stripe	Customers, payments, subscriptions, invoices
Clerk	Users, organizations, authentication
Notion	Pages, databases, workspace content
Jam	Bug reports, recordings, repro steps
Supermemory	Long-term memory and context
Attio	CRM records, lists, workspace data
Firetiger	Cloud tools and resources

GitHub, Linear, Sentry, and Postgres MCP servers are automatically available when you connect those integrations.

Custom servers

Bring your own MCP servers from the Integrations page using Custom MCP. Supports stdio, HTTP, and SSE, including OAuth.

Connection types

Remote (HTTP/SSE)

Use this for hosted MCP servers.

• Required: name, serverUrl
• Optional: static headers (for example, Authorization)
• If the server requires OAuth, Tembo returns an authorization URL and completes setup after you authorize

Stdio

Use this for command-based MCP servers started in the sandbox.

• Required: name, command
• Optional: args (space-separated in UI), env variables

Example:

{
  "type": "stdio",
  "name": "github-mcp",
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-github"],
  "env": {
    "GITHUB_TOKEN": "ghp_xxx"
  }
}