Integration

Fleet + MCP: 32 Tools for Claude Code and Any MCP Client

Name: Fleet
Author: Fleet

Fleet includes a built-in MCP server that exposes 32 tools over JSON-RPC on stdio. Run fleet mcp serve and point any MCP-compatible client at it — Claude Code discovers it automatically via .mcp.json in the repo root. The tools cover the full Fleet runtime surface: listing, creating, starting, and stopping agents; reading agent logs and output; publishing and reading fabric events; running and approving pipelines; assigning and updating tasks; reading the fleet log and dashboard; and surfacing brain insights.

This lets a Claude Code conversation query which agents are running, dispatch a task to a specific agent, check whether a PR was approved, or read recent fabric events without leaving the conversation. For anyone building on top of Fleet, the MCP server is also the cleanest programmatic interface to Fleet's state — it reads Fleet's SQLite database and configuration directly and does not require the watcher daemon to be running.

Setup

1

Install Fleet

curl -fsSL https://fleetctl.ai/install | sh

2

Start the MCP server (no flags)

fleet mcp serve

3

Register Fleet in your Claude Code MCP config (.mcp.json in the repo root)

{
  "mcpServers": {
    "fleet": {
      "command": "fleet",
      "args": ["mcp", "serve"]
    }
  }
}

What you gain

Any MCP-compatible client can query Fleet state, start and stop agents, and publish fabric events without shelling out to the CLI
Claude Code conversations get live access to fleet status, agent activity, pipeline state, and the fabric event log
32 tools cover the full Fleet runtime surface — agents, pipelines, fabric, tasks, config, and logs

Honest limits

The MCP server communicates over stdio; it serves a single client process and is not a network service
Tool behavior is built and tested against Claude Code; other MCP clients may need prompt adjustments to use the tools effectively
`fleet mcp serve` runs as a foreground process — it does not daemonize itself

Frequently asked questions

How many tools does the Fleet MCP server expose?

32 tools covering agent, pipeline, fabric, task, config, log, and dashboard operations. Claude Code discovers them automatically through .mcp.json.

Does the MCP server require a running watcher daemon?

No. `fleet mcp serve` reads Fleet's SQLite database and configuration directly. It runs as a foreground process and does not depend on the watcher being up.

More integrations

Fleet + GitHub →Fleet + Linear →Fleet + Jira →Fleet + tmux →Fleet + Git Worktrees →Fleet + CI/CD →

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.

See how it works Install Fleet