Claude Flow vs Swiss Living Index

A side-by-side look at the Claude Flow and Swiss Living Index 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 required
S
Swiss Living IndexDeveloper Tools · Remote HTTP/SSE
Official Swiss living-cost & relocation data for all 26 cantons — taxes, rent, premiums, jobs.39FairAuth: no auth required

Verdict: choose Claude Flow for coding agents work as a local process; choose Swiss Living Index 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.
  • Its auth model fits you: No auth required.
Explore Claude Flow

S
Choose Swiss Living Index when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Swiss Living Index

Feature & specification comparison

Rows where the two servers differ are marked.

SpecClaude Flow logoClaude Flow
S
Swiss Living Index
CategoryCoding AgentsDeveloper Tools
Quality signal49/100 · Fair39/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNo auth requiredNo auth required
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars79,057—
Directory activity 3 views 0 installs 0 upvotes 0 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.

Swiss Living Index 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"
      ]
    }
  }
}

Swiss Living Index

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "swiss-living-index": {
      "command": "npx",
      "args": [
        "-y",
        "swiss-living-index"
      ]
    }
  }
}

Frequently asked questions

Claude Flow is categorized under Coding Agents and uses a local stdio subprocess. Swiss Living Index belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Claude Flow for coding agents work and Swiss Living Index 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. Auth: no auth required. Swiss Living Index 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 claude-flow and swiss-living-index 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. Swiss Living Index has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.