Wellness Project vs Claude Flow

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

Wellness Project logoWellness ProjectDeveloper Tools · Remote HTTP/SSEHosted MCP server connecting Apple Health, Fitbit, Oura & Health Connect to Claude and ChatGPT.43FairAuth: oauth 2.0Claude Flow logoClaude FlowCoding Agents · Local subprocess (stdio)AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.53GoodAuth: not declared

Verdict: choose Wellness Project for developer tools work over a hosted endpoint; 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?

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecWellness Project logoWellness ProjectClaude Flow logoClaude Flow
CategoryDeveloper ToolsCoding Agents
Quality signal43/100 · Fair53/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthOAuth 2.0Not declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars277,526
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Wellness Project 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.

Wellness Project

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

Claude Flow

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

Frequently asked questions

Wellness Project is categorized under Developer Tools and uses a remote HTTP/SSE transport. Claude Flow belongs to Coding Agents and uses a local stdio subprocess. Pick Wellness Project for developer tools 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.

Wellness Project has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 wellness-project and claude-flow as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Wellness Project has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 2 GitHub stars. Claude Flow has 53/100 (Good) with 3 views, 0 installs and 77,526 GitHub stars.