Context Mode vs IAF Agent Bridge

A side-by-side look at the Context Mode 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.

Context Mode logoContext ModeCoding Agents · Local subprocess (stdio)Context window optimization for AI coding agents. Sandboxes tool output (98% reduction), persists session memory, and enforces routing across 17 platforms via MCP + hooks.69GreatAuth: no auth requiredIAF Agent Bridge logoIAF Agent BridgeCoding Agents · Local subprocess (stdio)MCP server that sends work to Cursor Agent over ACP and returns the session id needed to continue.60GoodAuth: not declared

Verdict: choose Context Mode 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?

Context Mode logoChoose Context Mode 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.
  • You want tools like ctx_batch_execute, ctx_execute, ctx_execute_file.
Explore Context Mode

IAF Agent Bridge logoChoose 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.
Explore IAF Agent Bridge

Feature & specification comparison

Rows where the two servers differ are marked.

SpecContext Mode logoContext ModeIAF Agent Bridge logoIAF Agent Bridge
CategoryCoding AgentsCoding Agents
Quality signal69/100 · Great60/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars32,0050
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools103

Tools & capabilities

Context Mode tools 10

  • ctx_batch_executeRun multiple commands + search multiple queries in ONE call. Opt-in `concurrency: 1-8` for I/O-bound batches.
  • ctx_executeRun code in 12 languages. Only stdout enters context.
  • ctx_execute_fileProcess files in sandbox. Raw content never leaves.
  • ctx_indexChunk markdown into FTS5 with BM25 ranking.
  • ctx_searchQuery indexed content with multiple queries in one call.
  • ctx_fetch_and_indexFetch URL, chunk and index. Cache reuses content within TTL (default 24h, override per-call with `ttl: <ms>`). `ttl: 0` or `force: true` to bypass. Pass `requests: [{url, source}, ...]` + `concurrency: 1-8` for parallel multi-URL.
  • ctx_statsShow context savings, call counts, and session statistics.
  • ctx_doctorDiagnose installation: runtimes, hooks, FTS5, versions.
  • ctx_upgradeUpgrade to latest version from GitHub, rebuild, reconfigure hooks.
  • ctx_purgePermanently deletes all indexed content from the knowledge base.

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.

Context Mode

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "context-mode": {
      "command": "npx",
      "args": [
        "-y",
        "context-mode"
      ]
    }
  }
}

IAF Agent Bridge

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "iaf-agent-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "iaf-agent-bridge"
      ]
    }
  }
}

Frequently asked questions

Context Mode 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 Context Mode 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.

Context Mode is listed as free. Auth: no auth required. 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 context-mode and iaf-agent-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Context Mode has a quality signal of 69/100 (Great) with 2 views, 0 installs and 32,005 GitHub stars. IAF Agent Bridge has 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars.