IAF Agent Bridge vs DesktopCommanderMCP
A side-by-side look at the IAF Agent Bridge and DesktopCommanderMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose IAF Agent Bridge for coding agents work as a local process; choose DesktopCommanderMCP 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 IAF Agent Bridge when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You want tools like
delegate, cancel, doctor.
Choose DesktopCommanderMCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 60/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 10,105 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View IAF Agent Bridge | View DesktopCommanderMCP |
Tools & capabilities
IAF Agent Bridge tools 3
delegateSend a prompt to Cursor Agent and wait until that Cursor turn is terminal, including tool work and any sub-agent follow-up Cursor performs before it stops. Returns Cursor's reply and the sessionId to reuse. A second call for a session that is still running is rejected. You decide CONTINUE, COMPLETE, or BLOCKED. Do not shell out to the agent binary.cancelCancel an in-flight Cursor turn by sessionId. Status is cancelled, killed, not-running (the turn ended and the session can still be resumed), or not-found.doctorReport Node, bridge version, Cursor CLI discovery, authentication state without secrets, and an optional ACP handshake.
DesktopCommanderMCP 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.
IAF Agent Bridge
{
"mcpServers": {
"iaf-agent-bridge": {
"command": "npx",
"args": [
"-y",
"iaf-agent-bridge"
]
}
}
}
DesktopCommanderMCP
{
"mcpServers": {
"wonderwhy-er-desktopcommandermcp": {
"command": "npx",
"args": [
"-y",
"@wonderwhy-er/desktop-commander@latest"
]
}
}
}
Frequently asked questions
IAF Agent Bridge is categorized under Coding Agents and uses a local stdio subprocess. DesktopCommanderMCP belongs to Coding Agents and uses a local stdio subprocess. Pick IAF Agent Bridge for coding agents work and DesktopCommanderMCP 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.
IAF Agent Bridge has no declared pricing — check the project's own site. DesktopCommanderMCP is listed as free. 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 iaf-agent-bridge and wonderwhy-er-desktopcommandermcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, IAF Agent Bridge has a quality signal of 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars. DesktopCommanderMCP has 56/100 (Good) with 3 views, 0 installs and 10,105 GitHub stars.