Documentation
ide-bridge is a local MCP daemon that stores a Portable Context Bundle per project and exposes six MCP tools. Any supported agentic IDE can save to or load from the bundle — so when you switch IDEs mid-task, the next agent turn starts already knowing what you were doing and why.
Getting started
Install the daemon, initialize your project, and run your first cross-IDE handoff in under 10 minutes.
Start with Install →Reference
Full reference for all 6 MCP tools, the .ide-bridge.yaml config file, environment variables, and per-IDE adapters.
Browse MCP tools →Help
Common errors, path conflicts, fidelity mismatches, and the "checkpoint saved but not visible" class of problems.
Troubleshooting →What's in the bundle?
Every ide-bridge project stores a single versioned JSON document called the Portable Context Bundle (PCB). It contains everything an agent needs to resume work: plan steps, decisions with rationale, open TODOs, git state (remote, branch, HEAD, diffs), and a rolling conversation summary. When the source IDE supports it, the last N verbatim turns are included too.
The daemon deep-merges incoming bundle fragments on every save_checkpoint call — arrays are appended, decisions and TODOs are deduplicated by ID, and writes are atomic (write-then-rename). The full schema and all six tools are documented in MCP tools.
Supported fidelity levels
Different IDEs can produce and consume different amounts of context. ide-bridge calls this the fidelity level:
- L0 — plan steps, decisions, TODOs, git state
- L1 — L0 + rolling conversation summary
- L2 — L1 + last-N verbatim turns
- L3 — full session resume (Claude Code only)
The daemon automatically picks min(source_fidelity, target_fidelity) on every handoff. See Adapters for the fidelity cap of each IDE.
Next: Install →