Expose the 5dive agent-fleet CLI (tasks, agents, digest) as MCP tools, over stdio or HTTP.
Expose the 5dive agent-fleet CLI as Model Context Protocol tools. Point any MCP client (Claude Desktop, Cursor, Cline, or your own) at this stdio server to file tasks, inspect and message agents, and read the fleet digest — directly from inside a model context.
5dive is the CLI + control plane for running a fleet of
autonomous coding agents as a self-governing company. This server is a thin,
honest adapter: every tool shells out to the local 5dive binary's
machine-readable --json surface and returns the result — so it inherits the
CLI's auth, permissions, and audit log for free, and never handles secrets itself.
| Tool | Wraps | What it does |
|---|---|---|
task_create | 5dive task add | File a task in the shared queue (title, body, priority, assignee, parent). |
task_show | 5dive task show | Full detail for one task by id (status, body, result, subtasks, blockers). |
task_list | 5dive task ls | List tasks (open by default; filter by status / assignee). |
agent_send | 5dive agent send | Send a message to another agent on the fleet. |
agent_list | 5dive agent list | List every agent: type, channels, model, live state. |
digest_get | 5dive digest | Fleet daily standup digest (window: "7d" for the weekly view). |
5dive CLI installed and on PATH (curl https://install.5dive.ai | sudo bash).npx @5dive/mcp # run directly
# or
npm i -g @5dive/mcp && 5dive-mcp
{
"mcpServers": {
"5dive": {
"command": "npx",
"args": ["-y", "@5dive/mcp"],
"env": { "FIVEDIVE_SUDO": "1" }
}
}
}
| Var | Default | Purpose |
|---|---|---|
FIVEDIVE_BIN | 5dive | Path to the 5dive binary. |
FIVEDIVE_SUDO | (unset) | Set to 1 to prefix calls with sudo. Managed 5dive boxes require root for most subcommands; leave unset if you already run as root. |
FIVEDIVE_TIMEOUT_MS | 30000 | Per-call timeout in milliseconds. |
Arguments are passed to the CLI as an argv array with no shell, so tool input can never be interpreted as shell syntax. The server never sees secrets: the CLI reads its own credentials from the box.
This mirrors a curated slice of the CLI (tasks, agents, digest), not its full
surface. It is a distribution and convenience layer, not a new API. For
everything else, use the 5dive CLI directly (5dive --help). Full docs: https://5dive.ai/docs/5dive-cli
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @5dive/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-5dive-ai-5dive-mcp": {
"command": "npx",
"args": [
"-y",
"@5dive/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@5dive/mcpnpmio.github.5dive-ai/5dive-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.