Claude Context Bridge

io.github.PhoenixFeuer32Published by GitHub account PhoenixFeuer32v2.0.0Updated Oct 24, 2026

Share context and questions between Claude instances — VS Code, claude.ai web, and mobile.

The publisher's own server: Claude Platform Docs

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP endpoint that lets Claude instances in VS Code, on claude.ai web and on mobile share context and questions with each other.

What you can do
Share context between separate Claude instances running in VS Code, on claude.ai web and on mobile, so work started in one place can be picked up in another. Pass questions between those instances rather than repeating them in each session. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you work with Claude across several surfaces, such as an editor and the web or mobile app, and want context or open questions to carry over between them instead of restating them each time.
Requirements
A remote streamable HTTP endpoint at claude-context-bridge.fly.dev; OAuth authentication is required. No environment variables, headers or packages are declared.
Before you install
Context and questions you share are sent to a third-party hosted service, so avoid putting secrets or sensitive material into shared context. Access is tied to an OAuth sign-in. The manifest lists no tools, so what is stored and who can read it is not documented here.

Installation

In SourceWeft

  1. Open Claude Context Bridge in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.PhoenixFeuer32%2Fclaude-context-bridge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "claude-context-bridge": {
      "type": "http",
      "url": "https://claude-context-bridge.fly.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Claude integrations