
Claude Context Bridge
Carry the same thread context and open questions between Claude in VS Code, claude.ai on the web, and mobile without re-pasting long prompts.
Overview
Claude Context Bridge is a MCP server for the Build phase that shares context and questions between Claude in VS Code, claude.ai web, and mobile.
What is this MCP server?
- Sync context and questions across VS Code, claude.ai web, and mobile Claude surfaces
- Hosted streamable HTTP MCP at claude-context-bridge.fly.dev with API_KEY variable
- Version 2.0.0 with GitHub source repository for self-host or inspection
- API keys generated via npm run generate-key for client configuration
- Registry version 2.0.0
- Remote URL https://claude-context-bridge.fly.dev/mcp
- GitHub repository PhoenixFeuer32/claude-context-bridge
What problem does it solve?
Switching Claude clients forces you to re-explain the project and lose follow-up questions mid-build.
Who is it for?
Solo builders who split time between Claude Code in the IDE and mobile or web Claude for quick decisions.
Skip if: Teams that standardize on one client only, or builders who cannot use a hosted context relay for sensitive code.
What do I get? / Deliverables
After connecting the bridge MCP with an API key, the same context and question state is available whichever Claude surface you open.
- Shared context state across Claude clients
- Persisted questions readable from any connected surface
- Reduced re-prompting when switching devices
Recommended MCP Servers
Journey fit
Build phase agent-tooling is the natural shelf because the server exists to unify how you work with Claude across clients while you are actively shipping code and specs. Agent-tooling covers cross-surface MCP bridges that extend your default Claude Code or IDE setup rather than replacing app backend logic.
How it compares
Cross-client context sync MCP, not a repo indexer or generic chat export skill.
Common Questions / FAQ
Who is Claude Context Bridge for?
Developers using multiple Claude surfaces who want one shared context channel instead of copy-pasting between VS Code, web, and mobile.
When should I use Claude Context Bridge?
Use it when you start a task in the IDE and need to continue or clarify on claude.ai without rebuilding context from scratch.
How do I add Claude Context Bridge to my agent?
Generate an API key with npm run generate-key, add the remote https://claude-context-bridge.fly.dev/mcp as streamable HTTP, and set API_KEY in your MCP client variables.