Model Context Protocol

MCP servers extend Tembo agents with additional tools, integrations, and capabilities. Connect to external systems, APIs, and data sources.

Get StartedView docs

Built-in MCP Servers

These MCP servers come pre-configured and ready to use with every Tembo workspace.

Tembo MCP

stdio

Core Tembo functionality for task management and collaboration.

  • Create sub-issues from tasks
  • Send Slack messages
  • List and filter tasks

Playwright MCP

stdio

Browser automation for testing and web interactions.

  • Navigate and screenshot
  • Fill forms and click elements
  • Run automated tests

Context7 MCP

stdio

Enhanced context management and semantic search.

  • Improved context retrieval
  • Semantic code search
  • Cross-file understanding

Integration MCPs

These MCPs are automatically available when you connect the corresponding integration.

View all integrations

GitHub

Repository management, issues, and pull requests

Linear

Issue tracking and project management

Notion

Pages, databases, and workspace access

Connection Protocols

Tembo supports three protocols for connecting to MCP servers.

stdio

Local process-based servers

Run MCP servers as local processes. Best for built-in tools and local development.

http

Remote HTTP servers

Connect to MCP servers over HTTP. Ideal for shared services and remote APIs.

sse

Server-Sent Events

Real-time streaming connections. Perfect for live data and event-driven tools.

Configuration

Add custom MCP servers in Settings → Agents → Custom MCP Servers. Tembo accepts JSON configuration with named servers.

Read the docs
{
  "my-custom-mcp": {
    "type": "stdio",
    "command": "node",
    "args": ["./mcp-server.js"]
  },
  "remote-api": {
    "type": "http",
    "url": "https://api.example.com/mcp",
    "headers": {
      "Authorization": "Bearer $API_KEY"
    }
  }
}

Best Practices

Follow these guidelines for secure and maintainable MCP configurations.

Use environment variables

Store API keys and credentials as environment variables, never hardcode them in configurations.

Test locally first

Validate your MCP server configuration locally before deploying to your organization.

Document your MCPs

Keep configurations in version control and document what each MCP does for your team.

Monitor usage

Track which MCPs are being used and their performance to optimize your setup.