MCP Server
Connect Claude Desktop, Cursor, VS Code, and other MCP-compatible clients to Dobby. 91 tools for managing tasks, approvals, agents, GitHub, Jira, and more — directly from your IDE.
What You Can Do
Manage tasks from your IDE
Create, assign, and track agent tasks without leaving Claude Desktop or Cursor.
Approve agent actions
Review and approve pending agent requests directly from your development environment.
Monitor agent health
Check service status, view active issues, and access the operations audit trail.
Automate workflows
Search GitHub/Jira, manage schedules, run CrewAI crews, and query knowledge bases.
Quick Setup
Prerequisites
You need a Dobby account with a Gateway API key. Keys are created in your workspace dashboard under Settings > Gateway.
{
"mcpServers": {
"dobby": {
"command": "npx",
"args": [
"-y",
"@dobbyai/mcp-external"
],
"env": {
"DOBBY_API_URL": "https://dobby-ai.com",
"DOBBY_API_KEY": "<YOUR_GATEWAY_KEY>",
"DOBBY_TENANT_ID": "<YOUR_TENANT_ID>",
"DOBBY_ORG_ID": "<YOUR_ORG_ID>"
}
}
}
}Replace <YOUR_GATEWAY_KEY>, <YOUR_TENANT_ID>, and <YOUR_ORG_ID> with your actual credentials from the dashboard.
Available Tools
70 tools across 13 categories. Click a category to see all tools.
Authentication
All MCP requests are authenticated via your Gateway API key. Three key tiers are available:
| Prefix | Type | Rate Limit | Best For |
|---|---|---|---|
| gk_user_* | User | 100 RPM | IDE / personal use |
| gk_svc_* | Service | 500 RPM | Automated agents / CI |
| gk_tmp_* | Temporary | 50 RPM | Testing / demos (auto-expire) |
MCP tools require mcp:read and mcp:execute scopes. These are included by default when creating a key.
Security
Authenticated access — every MCP request validates your Gateway key with scope-level permissions
Full audit trail — every tool invocation is logged with actor, timestamp, and result
Regional data residency — your data stays in your selected region (Israel, EU, or US)
Kill-switch — organization admins can instantly block all MCP access via the kill-switch