Wiff vs Agent MCP
A side-by-side look at the Wiff and Agent MCP 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 Agent MCP for coding agents over a hosted endpoint. 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 Agent MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, AGENT_MCP_HOST, AGENT_MCP_PORT, AGENT_MCP_LOG_LEVEL, AGENT_MCP_PROJECT_DIR, AGENT_MCP_MAX_AGENTS. - You want tools like
create_agent, list_agents, terminate_agent.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 60/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | WIFF_BACKEND | OPENAI_API_KEYAGENT_MCP_HOSTAGENT_MCP_PORTAGENT_MCP_LOG_LEVELAGENT_MCP_PROJECT_DIRAGENT_MCP_MAX_AGENTS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 1,304 |
| Directory activity | 4 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | 12 |
| Full listing | View Wiff | View Agent MCP |
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.
Agent MCP tools 12
create_agentlist_agentsterminate_agentassign_taskview_tasksupdate_task_statusask_project_ragupdate_project_contextview_project_contextsend_agent_messagebroadcast_messagerequest_assistance
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"
}
}
}
}
Agent MCP
{
"mcpServers": {
"rinadelph-agent-mcp": {
"url": "http://localhost:8000/mcp"
}
}
}
Frequently asked questions
Wiff is categorized under Coding Agents and uses a local stdio subprocess. Agent MCP belongs to Coding Agents and uses a remote HTTP/SSE transport. Pick Wiff for coding agents work and Agent MCP 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.
Wiff has no declared pricing — check the project's own site. Agent MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 rinadelph-agent-mcp 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. Agent MCP has 60/100 (Good) with 5 views, 0 installs and 1,304 GitHub stars.