Skip to main content
MCP (Model Context Protocol) servers extend your agents with additional tools, integrations, and capabilities. Tembo supports both built-in MCP servers and custom configurations.

​
What is MCP?

The Model Context Protocol is an open standard that allows AI agents to connect to external tools, APIs, and data sources. MCP servers provide tools that your agents can use to interact with external systems, from browser automation to project management integrations. Learn more at modelcontextprotocol.io.

​
Built-in MCP Servers

Tembo provides several MCP servers out of the box:
ServerTypeDescription
PlaywrightstdioBrowser automation and web testing
Context7stdioContext management and search

​
Playwright MCP

Enables agents to automate browser interactions:
  • Navigate web pages
  • Fill forms and click elements
  • Take screenshots
  • Run automated tests

​
Context7 MCP

Provides enhanced context management capabilities for your agents.

​
Integration MCP Servers

When you connect integrations to Tembo, additional MCP servers become available automatically:
IntegrationServer TypeTools Provided
GitHubstdioRepository management, issues, pull requests
LinearhttpIssue tracking, project management
NotionhttpPages, databases, blocks, workspace structure
PostgreshttpRead-only database queries, schema, performance stats
These servers are automatically configured with the appropriate authentication when you connect the integration.

​
Custom MCP Servers

You can add custom MCP servers in your organization settings. Tembo supports three types of MCP servers:

​
Server Types

stdio - Local process-based servers 
{
  "command": "node",
  "args": ["path/to/server.js"],
  "env": {
    "API_KEY": "your-key"
  }
}
http - HTTP-based servers 
{
  "url": "https://example.com/mcp",
  "headers": {
    "Authorization": "Bearer token"
  }
}
sse - Server-Sent Events servers 
{
  "url": "https://example.com/mcp/sse",
  "headers": {
    "Authorization": "Bearer token"
  }
}

​
Configuration Format

Custom MCP servers support two JSON formats: Object format (recommended) - keyed by server name: 
{
  "mcpServers": {
    "my-server": { "command": "node", "args": ["server.js"], "env": { "API_KEY": "key" } },
    "api-server": { "url": "https://api.example.com/mcp" }
  }
}
Array format - explicit name and type fields: 
{
  "mcpServers": [
    { "name": "my-server", "type": "stdio", "command": "node", "args": ["server.js"] },
    { "name": "api-server", "type": "http", "url": "https://api.example.com/mcp" }
  ]
}

​
Adding Custom MCP Servers

To add custom MCP servers to your organization:
  1. Navigate to Settings > Models in your Tembo dashboard
  2. Scroll to the Custom MCP Servers section
  3. Enter your MCP configuration in JSON format
  4. Press Cmd+Enter (Mac) or Ctrl+Enter (Windows/Linux) to save
  5. New tasks will automatically use the configured MCP servers

​
Best Practices

  • Security — Store credentials as environment variables, not hardcoded in configuration
  • Testing — Test MCP servers locally before adding to your organization
  • Documentation — Document custom servers for your team (tools provided, when to use)
  • Version Control — Keep configurations alongside rule files for team consistency

​
Troubleshooting

  • Server not available? Check that configuration is valid JSON with all required fields.
  • Authentication errors? Verify credentials and API keys have necessary permissions.
  • Connection issues? Ensure HTTP/SSE URLs are accessible and servers are running.
For help, contact support.