Tembo MCP Server
Official<p align="center">
<img src="https://github.com/user-attachments/assets/2d6b9c98-5c2a-4022-a48a-c07058149fc5" alt="Tembo app icon" width="250" height="250">
</p>
# Tembo MCP Server
An [MCP server](https://spec.modelcontextprotocol.io/) for the [Tembo](https://tembo.io) [API](https://docs.tembo.io/api-reference/public-api/).
## Features
This MCP server provides the following tools:
- **create_task** - Create new tasks in Tembo with optional repository and branch targeting
- **list_tasks** - Get a paginated list of tasks for your organization
- **search_tasks** - Search for tasks by query string in title or description
- **list_repositories** - Get enabled code repositories for your organization
- **get_current_user** - Retrieve information about the authenticated user
## Installation
### Using npx
```bash
npx -y @tembo-io/mcp
```
### Installing globally
```bash
npm install -g @tembo-io/mcp
```
## Usage
### 1. Get an API Key
Head to the [API Keys page](https://app.tembo.io/settings/api-keys) and obtain a new key to use with the MCP server.
### 2. Configure Your MCP Client
Add the following configuration to your MCP client settings (e.g., Claude Desktop's `claude_desktop_config.json`):
```json
{
"mcpServers": {
"tembo": {
"command": "npx",
"args": ["-y", "@tembo-io/mcp"],
"env": {
"TEMBO_API_KEY": "your-api-key"
}
}
}
}
```TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: create_task, get_current_user, list_repositories, list_tasks, and search_tasks target different resources and actions. The descriptions reinforce this separation, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent verb_noun pattern (e.g., create_task, get_current_user, list_repositories, list_tasks, search_tasks). There are no deviations in style or convention, making the set predictable and readable.
With 5 tools, the count is reasonable and well-scoped for a task management server, though it feels slightly thin. Each tool earns its place, but there might be room for additional operations like update_task or delete_task to enhance coverage without being excessive.
The tool surface covers core operations like creating, listing, and searching tasks, but has notable gaps in task lifecycle management (e.g., no update_task or delete_task). While agents can work around this for basic workflows, the lack of full CRUD coverage limits completeness for the task management domain.