Spec Driven Development vs Wiff
A side-by-side look at the Spec Driven Development and Wiff MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Spec Driven Development for coding agents work as a local process; choose Wiff 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 Spec Driven Development when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 44/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | WIFF_BACKEND |
| Verified owner | Community listing | Community listing |
| GitHub stars | 439 | 5 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Spec Driven Development | View Wiff |
Tools & capabilities
Spec Driven Development tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Spec Driven Development
{
"mcpServers": {
"spec-driven-development": {
"command": "npx",
"args": [
"-y",
"mcp-server-spec-driven-development@latest"
]
}
}
}
Wiff
{
"mcpServers": {
"wiff": {
"command": "npx",
"args": [
"-y",
"@xxxoooxoxo/wiff"
],
"env": {
"WIFF_BACKEND": "YOUR_WIFF_BACKEND_HERE"
}
}
}
}
Frequently asked questions
Spec Driven Development is categorized under Coding Agents and uses a local stdio subprocess. Wiff belongs to Coding Agents and uses a local stdio subprocess. Pick Spec Driven Development for coding agents work and Wiff 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.
Spec Driven Development has no declared pricing — check the project's own site. Wiff 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 spec-driven-development and wiff as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Spec Driven Development has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 439 GitHub stars. Wiff has 60/100 (Good) with 4 views, 0 installs and 5 GitHub stars.