Agent Fleet O MCP Server

Connect Agent Fleet O to Claude, Cursor or any other MCP client and it stops being a tab you switch to. ☁️ Prefer managed? Try FleetQ Cloud — zero setup, free tier. ⭐ Like the project? Give it a star on GitHub — it helps others find FleetQ. The agent fleet o mcp server is what makes that connection.

What the server does

• 🔁 Visual DAG workflows with 8 node types (agent, conditional, human-task, switch, dynamic-fork, do-while, compensation, sub-workflow) — no Python glue code
• 👥 Multi-agent crews with coordinator/worker/reviewer roles, weighted QA scoring, and cross-validation
• 🛡️ Real-World Action governance — assistant tool calls, integration writes, and git pushes route through a per-tier risk policy (auto / ask / reject for low / medium / high). Approvals auto-execute. Audit trail attached
• 💰 Budget controls with a real credit ledger, pessimistic locking, and auto-pause on overspend — not just token counters
• 🧠 Agent evolution — LLM analyzes execution history and proposes config changes you approve with one click
• ⚙️ BYOK + Local LLMs — Anthropic, OpenAI, Google, plus Ollama, LM Studio, vLLM, Codex, Claude Code. Zero vendor lock-in

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Real — World Action governance** — ActionProposal flow gates assistant tool calls, integration writes, and git pushes through a per-tier risk policy with
• Per — tool deadlines** — optional deadline_ms parameter on every MCP tool; agents can bound wall-clock time per call
• Infrastructure — The Infrastructure tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: REDIS_HOST, ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_AI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agent Fleet O's toolset — Real, Per, Infrastructure — is a fair guide to whether it matches your workflow. It is maintained by escapeboy; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.