Fleet 1.13:Teams are now shipping 5x more PRs with autonomous pipelines.See what's new →
FleetFleet
CLI reference

fleet mcp

fleet mcp serve

Starts the Fleet MCP server, which exposes 32 tools over JSON-RPC 2.0 on stdio. Claude Code auto-discovers the server via .mcp.json in the repository root and makes Fleet operations available as native tools within the session, so the user does not have to type CLI commands.

The MCP server covers fleet, agent, pipeline, fabric, watch, task, config, and log operations. It is the primary integration point between Fleet and Claude Code. It is typically launched by Claude Code, not by hand, and takes no flags.

Examples

Start the MCP server on stdio (usually invoked by Claude Code, not manually)

fleet mcp serve

Wire the server in .mcp.json so Claude Code discovers it

cat .mcp.json
# {"mcpServers":{"fleet":{"command":"fleet","args":["mcp","serve"]}}}

Frequently asked questions

How many tools does the MCP server expose?

32 tools, covering status, doctor, dashboard, agent, pipeline, fabric, watch, task, config, brain insights, and log operations.

Does fleet mcp serve take any flags?

No. The only valid invocation is `fleet mcp serve`. It reads and writes JSON-RPC on stdio.

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.