Claude Flow vs Dibs

A side-by-side look at the Claude Flow and Dibs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Claude Flow logoClaude FlowCoding Agents · Local subprocess (stdio)AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.49FairAuth: no auth requiredDibs logoDibsCoding Agents · Local subprocess (stdio)Coordination layer for parallel coding agents: TTL file claims stored in the git common dir (visible across every worktree instantly), enforcement hooks that block colliding edits in Claude Code and at commit time, agent presence, handoff notes, and git-committed lessons searchable with BM25. Single static binary — no server, no database.53GoodAuth: not declared

Verdict: choose Claude Flow for coding agents work as a local process; choose Dibs 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?

Claude Flow logoChoose Claude Flow when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Claude Flow

Dibs logoChoose Dibs when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: DIBS_AGENT.
Explore Dibs

Feature & specification comparison

Rows where the two servers differ are marked.

SpecClaude Flow logoClaude FlowDibs logoDibs
CategoryCoding AgentsCoding Agents
Quality signal49/100 · Fair53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingNot declaredNot declared
Required env varsNone listedDIBS_AGENT
Verified ownerCommunity listingCommunity listing
GitHub stars79,0572
Directory activity 3 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Claude Flow tools

No tool names declared yet. Check the project README from the listing page.

Dibs 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.

Claude Flow

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "claude-flow": {
      "command": "npx",
      "args": [
        "-y",
        "ruflo@latest"
      ]
    }
  }
}

Dibs

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "polymatx-dibs": {
      "command": "npx",
      "args": [
        "-y",
        "dibs"
      ],
      "env": {
        "DIBS_AGENT": "YOUR_DIBS_AGENT_HERE"
      }
    }
  }
}

Frequently asked questions

Claude Flow is categorized under Coding Agents and uses a local stdio subprocess. Dibs belongs to Coding Agents and uses a local stdio subprocess. Pick Claude Flow for coding agents work and Dibs 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.

Claude Flow has no declared pricing — check the project's own site. Auth: no auth required. Dibs 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 claude-flow and polymatx-dibs as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Claude Flow has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 79,057 GitHub stars. Dibs has 53/100 (Good) with 3 views, 0 installs and 2 GitHub stars.