A side-by-side look at the Vibe Gate MCP and Claude Flow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vibe Gate MCP 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?
Choose Vibe Gate MCP when
You need dedicated capabilities in the Coding Agents domain.
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.
Vibe Gate MCP is categorized under Coding Agents and uses a local stdio subprocess. Claude Flow belongs to Coding Agents and uses a local stdio subprocess. Pick Vibe Gate MCP 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.
Vibe Gate MCP has no declared pricing — check the project's own site. 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 vibe-gate-mcp and claude-flow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vibe Gate MCP has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Claude Flow has 53/100 (Good) with 3 views, 0 installs and 77,526 GitHub stars.