Claude Flow vs Wellness Project

A side-by-side look at the Claude Flow and Wellness Project 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.53GoodAuth: not declaredWellness Project logoWellness ProjectDeveloper Tools · Remote HTTP/SSEHosted MCP server connecting Apple Health, Fitbit, Oura & Health Connect to Claude and ChatGPT.43FairAuth: oauth 2.0

Verdict: choose Claude Flow for coding agents work as a local process; choose Wellness Project for developer tools over a hosted endpoint. 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.
Explore Claude Flow

Wellness Project logoChoose Wellness Project when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Wellness Project

Feature & specification comparison

Rows where the two servers differ are marked.

SpecClaude Flow logoClaude FlowWellness Project logoWellness Project
CategoryCoding AgentsDeveloper Tools
Quality signal53/100 · Good43/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars77,5262
Directory activity 3 views 0 installs 0 upvotes 1 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.

Wellness Project 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"
      ]
    }
  }
}

Wellness Project

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "wellness-project": {
      "url": "https://wellnessproject.ai/api/mcp"
    }
  }
}

Frequently asked questions

Claude Flow is categorized under Coding Agents and uses a local stdio subprocess. Wellness Project belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Claude Flow for coding agents work and Wellness Project for developer tools.

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. Wellness Project has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 wellness-project 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 53/100 (Good) with 3 views, 0 installs and 77,526 GitHub stars. Wellness Project has 43/100 (Fair) with 1 views, 0 installs and 2 GitHub stars.