M1nd vs Claude Flow

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

M1nd logoM1ndCoding Agents · Local subprocess (stdio)The shell around your coding agent: a neuro-symbolic code graph with calibrated trust, via MCP.47FairAuth: not declaredClaude 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 required

Verdict: choose M1nd 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?

M1nd logoChoose M1nd when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
Explore M1nd

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecM1nd logoM1ndClaude Flow logoClaude Flow
CategoryCoding AgentsCoding Agents
Quality signal47/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2379,057
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

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

M1nd

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "m1nd": {
      "command": "npx",
      "args": [
        "-y",
        "@maxkle1nz/m1nd@1.6.5"
      ]
    }
  }
}

Claude Flow

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

Frequently asked questions

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

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

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