Dobby
Wire your coding agent to Dobby so you can queue tasks, require human approvals, run schedules, and enforce governance from the IDE instead of a separate ops console.
Overview
Dobby is an Operate-phase MCP server that lets coding agents connect to the Dobby platform to manage tasks, approvals, schedules, and governance for AI workers.
What is this MCP server?
- stdio MCP via npm @dobbyai/mcp-external (v1.1.0) or remote streamable-http at https://mcp.dobby-ai.com/mcp
- Task and schedule management for AI agents from the agent session
- Human-in-the-loop approvals and governance hooks for agent actions
- Requires DOBBY_API_KEY (dk_* or gk_*) and DOBBY_TENANT_ID; optional DOBBY_API_URL
- MCP integration to the Dobby platform—not a standalone agent skill or local script
- Registry version 1.1.0
- Two transports: npm stdio package and remote streamable-http URL
- Three documented environment variables (two required)
What problem does it solve?
You cannot safely run autonomous agents at scale when every status check and approval lives outside the tool where you actually steer the agent.
Who is it for?
Solo builders or tiny teams already on Dobby who want MCP-driven task queues, schedules, and approval flows from Claude Code or Cursor.
Skip if: Builders who only need local file edits and have no Dobby workspace, or anyone who wants payments or AWS emulation instead of agent ops.
What do I get? / Deliverables
After you register the MCP server with your API key and tenant ID, your agent can orchestrate and monitor Dobby-managed work from the same session where you code and debug.
- Live MCP connection to your Dobby tenant for agent task and schedule control
- Approval and governance actions callable from the agent session
- Optional remote MCP endpoint without local npm install
Recommended MCP Servers
Journey fit
Dobby is about running and overseeing agents in production—tasks, approvals, and policy— which maps to the Operate phase rather than one-off build work. Monitoring is the canonical shelf because the server’s core story is connect, monitor, and control agents over time, not provisioning cloud resources.
How it compares
Hosted agent control-plane MCP, not a local dev tool or payment rail.
Common Questions / FAQ
Who is Dobby MCP for?
Indie builders and small teams using the Dobby platform who want their coding agent to assign tasks, monitor runs, and enforce approvals without leaving the IDE.
When should I use Dobby MCP?
Use it in the Operate phase when agents run recurring or production workflows and you need governance, scheduling, and visibility from MCP-capable clients.
How do I add Dobby MCP to my agent?
Install @dobbyai/mcp-external from npm for stdio, set DOBBY_API_KEY and DOBBY_TENANT_ID (and DOBBY_API_URL if self-hosted), or point your client at the remote URL https://mcp.dobby-ai.com/mcp for streamable HTTP.