Agent Swarm vs IAF Agent Bridge
A side-by-side look at the Agent Swarm and IAF Agent Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Swarm for coding agents work; choose IAF Agent Bridge 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 Agent Swarm when
- You need dedicated capabilities in the Coding Agents domain.
- You have the keys it needs:
API_KEY, HARNESS_PROVIDER.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 41/100 · Fair | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | API_KEYHARNESS_PROVIDER | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 929 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Agent Swarm | View IAF Agent Bridge |
Tools & capabilities
Agent Swarm tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Agent Swarm
No confirmed install command for Agent Swarm yet — follow the setup steps linked from its listing page rather than a guessed package name.
IAF Agent Bridge
{
"mcpServers": {
"iaf-agent-bridge": {
"command": "npx",
"args": [
"-y",
"iaf-agent-bridge"
]
}
}
}
Frequently asked questions
Agent Swarm is categorized under Coding Agents and uses an install path we have not confirmed yet. IAF Agent Bridge belongs to Coding Agents and uses a local stdio subprocess. Pick Agent Swarm for coding agents work and IAF Agent Bridge 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. Agent Swarm has no confirmed install command yet — follow its own setup instructions.
Agent Swarm has no declared pricing — check the project's own site. IAF Agent Bridge 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 agent-swarm and iaf-agent-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Swarm has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 929 GitHub stars. IAF Agent Bridge has 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars.