Fleet 2.9.1 is out.See what's new →
FleetFleet
MCP solutions

26 Fleet MCP tool solutions for any MCP client

Fleet turns its Model Context Protocol integration into concrete developer workflows: local agent control, pipeline gates, Fabric Event Bus handoffs, Brain Daemon insight, task routing, issue watches, and config management from Claude Code, Codex, OpenCode, or any other MCP client.

Self-hosted

Claude Code, Codex, OpenCode, and other MCP clients talk to `fleet mcp serve` over stdio, or to hosted Streamable HTTP. No extra network port for the local transport.

Audit trail

Fabric events, pipeline approvals, task updates, and agent activity remain queryable after the prompt ends.

Loop engineering

Each tool turns a repeated management prompt into a reusable local workflow.

Choose the tool-sized entry point

Every page maps one MCP tool to the developer problem it solves, an example prompt, and the guardrail Fleet keeps around the action.

Fleet & Status Tools

Inspect health, diagnostics, logs, dashboards, and Brain insights.

Agent Tools

Create, inspect, start, stop, and remove Fleet-managed agents.

Fabric Tools

Publish coordination events and inspect pending inbox deliveries.

Watch Tools

Notify an agent when a watched GitHub issue closes.

Task & Context Tools

Assign work and inspect or update Fabric task state.

Configuration Tools

Read and update local Fleet settings.

Workflow Tools

Inspect and update saved control-plane workflow execution settings.

Connect any MCP client to Fleet

Install the local binary, add `.mcp.json` or the hosted Streamable HTTP URL, and give Claude Code, Codex, OpenCode, or any other MCP client local tools for managing your agent fleet.