Wiff vs Claude Flow
A side-by-side look at the Wiff 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 Wiff for coding agents work as a local process; choose Claude Flow for coding agents. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Wiff when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
WIFF_BACKEND. - You want tools like
workflow_start, workflow_status, workflow_wait.
Choose Claude Flow when
- You need dedicated capabilities in the Coding Agents domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 60/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | WIFF_BACKEND | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 78,642 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Wiff | View Claude Flow |
Tools & capabilities
Wiff tools 5
workflow_startLaunch a deterministic JavaScript workflow in the background, or resume a previous run without repeating successful unchanged agent calls. User and project preferences are loaded from Wiff config. Always pass the caller's absolute working directory as cwd.workflow_statusRead the latest persisted status, phase, counters, result, and artifact paths for a workflow run.workflow_waitWait until a workflow changes state or the timeout elapses. Call repeatedly until the run is completed, failed, cancelled, or interrupted.workflow_cancelInterrupt all live agents and mark a workflow run cancelled.workflow_modelsList the models each agent backend (codex, claude, cursor, kimi) can run, with supported reasoning efforts. Backends that are unavailable on this machine report an error instead of models.
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.
Wiff
{
"mcpServers": {
"wiff": {
"command": "npx",
"args": [
"-y",
"@xxxoooxoxo/wiff"
],
"env": {
"WIFF_BACKEND": "YOUR_WIFF_BACKEND_HERE"
}
}
}
}
Claude Flow
No confirmed install command for Claude Flow yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Wiff is categorized under Coding Agents and uses a local stdio subprocess. Claude Flow belongs to Coding Agents and uses an install path we have not confirmed yet. Pick Wiff 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. Claude Flow has no confirmed install command yet — follow its own setup instructions.
Wiff 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 wiff and claude-flow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Wiff has a quality signal of 60/100 (Good) with 4 views, 0 installs and 5 GitHub stars. Claude Flow has 44/100 (Fair) with 3 views, 0 installs and 78,642 GitHub stars.