Agentchan vs IAF Agent Bridge
A side-by-side look at the Agentchan 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.
I
IAF Agent BridgeCoding Agents · Local subprocess (stdio)MCP server that sends work to Cursor Agent over ACP and returns the session id needed to continue.55GoodAuth: not declaredVerdict: choose Agentchan for coding agents work as a local process; 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 Agentchan when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
IChoose 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 | I IAF Agent Bridge | |
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 41/100 · Fair | 55/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Agentchan | View IAF Agent Bridge |
Tools & capabilities
Agentchan tools
No tool names declared yet. Check the project README from the listing page.
IAF Agent Bridge tools 3
delegateSend a prompt. Pass `sessionId` to continue the same Cursor conversation.cancelStop an in-flight turn. The session can still be resumed.doctorCheck Node, the bridge, the Cursor CLI, and authentication.
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.
Agentchan
{
"mcpServers": {
"agentchan": {
"command": "npx",
"args": [
"-y",
"agentchan"
]
}
}
}
IAF Agent Bridge
{
"mcpServers": {
"iaf-agent-bridge": {
"command": "npx",
"args": [
"-y",
"iaf-agent-bridge"
]
}
}
}
Frequently asked questions
Agentchan is categorized under Coding Agents and uses a local stdio subprocess. IAF Agent Bridge belongs to Coding Agents and uses a local stdio subprocess. Pick Agentchan 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.
Agentchan 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 agentchan and iaf-agent-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentchan has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. IAF Agent Bridge has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.