Agency Orchestrator vs Claude Flow
A side-by-side look at the Agency Orchestrator and Claude Flow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agency Orchestrator for coding agents work as a local process; choose Claude Flow for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agency Orchestrator when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Choose Claude Flow when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 55/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,397 | 77,526 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Agency Orchestrator | View Claude Flow |
Tools & capabilities
Agency Orchestrator tools
No tool names declared yet. Check the project README from the listing page.
Claude Flow tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agency Orchestrator
{
"mcpServers": {
"agency-orchestrator": {
"command": "npx",
"args": [
"agency-orchestrator"
]
}
}
}
Claude Flow
{
"mcpServers": {
"claude-flow": {
"command": "npx",
"args": [
"-y",
"ruflo@latest"
]
}
}
}
Frequently asked questions
Agency Orchestrator is categorized under Coding Agents and uses a local stdio subprocess. Claude Flow belongs to Coding Agents and uses a local stdio subprocess. Pick Agency Orchestrator for coding agents work and Claude Flow for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agency Orchestrator has no declared pricing — check the project's own site. Claude Flow has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agency-orchestrator and claude-flow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agency Orchestrator has a quality signal of 55/100 (Good) with 0 views, 0 installs and 2,397 GitHub stars. Claude Flow has 53/100 (Good) with 3 views, 0 installs and 77,526 GitHub stars.