Claude Bridge MCP server

claude-code-bridge-mcp

MCP server that pipes Claude Code session output directly into Claude Chat — no more copy-paste between tools.

claude-code-bridge-mcp is a Model Context Protocol (MCP) server that reads Claude Code's local session logs from ~/.claude/projects// and exposes them as tools to any MCP-compatible client (Claude Desktop, Claude Chat, Cursor, etc.). Run Claude Code in your terminal and pull its latest output into Claude Chat with a single tool call.

Features

• getlatestoutput — grab the most recent assistant message from any (or the most-recent) Claude Code session.
• listsessions** — enumerate all local sessions with project path, message count, and timestamps.
• getsessioncontext — fetch the last N messages from a session for context injection.
• watchsession** — poll a session file every 2 seconds and drain new messages on demand.
• writecontext (v2)_ — snapshot the last N messages into ~/.claude/bridge-context.md and ~/Documents/claude-bridge-context.md as clean markdown.
• startautosync (v2) — keep that markdown snapshot live: rewrites both files every 30 seconds (configurable) so a synced folder stays current without manual calls.
• setupdrivesync (v2.1) — authorize direct Google Drive upload. Each sync tick then upserts a Google Doc named claude-bridge-context via the Drive API — no Drive desktop client required.
• sendtosession (v2.2) — queue a prompt for a specific Claude Code session via a cooperative inbox at ~/.claude/bridge-inbox/.txt. Closes the read-only gap: Projects Claude → inbox → Claude Code acts on it.

What's new in v2.2 — sendtosession (cooperative dispatch)

v1 read sessions. v2 wrote context out to Drive. v2.2 lets the other side push prompts back in.

sendtosession overwrites ~/.claude/bridge-inbox/.txt with the latest prompt and writes a human-readable receipt to ~/.claude/bridge-inbox/latest.md. The target Claude Code session picks it up via a one-time setup instruction that sendtosession returns in its response — paste that once into your Claude Code terminal (or add it to your project's CLAUDE.md) and every subsequent prompt arrives automatically.

Why cooperative instead of direct injection: Claude Code's JSONL is append-only from the CLI's perspective — it doesn't re-read the file mid-session. A real dispatch channel exists (POST /v1/sessions/{id} via Anthropic's relay, the same channel /remote-control uses) but is undocumented and requires reading the CLI's OAuth token from the macOS Keychain. Shipping against an undocumented internal API would break on every Claude Code release and leak credentials from every install — so v2.2 uses the filesystem inbox instead. See GitHub issue for the v3 path.

Example:

// send_to_session → response
{
  "session_id": "15ef12ba-851e-4591-bbd4-c23170e15919",
  "project_path": "/Users/you/Documents/my-app",
  "written": true,
  "inbox_path": "/Users/you/.claude/bridge-inbox/15ef12ba-....txt",
  "receipt_path": "/Users/you/.claude/bridge-inbox/latest.md",
  "prompt_preview": "refactor the auth middleware to use Fluid Compute",
  "setup_instruction": "Before each response, check ~/.claude/bridge-inbox/15ef12ba-....txt — if it exists and is non-empty, read its contents, delete the file, and treat those contents as your next user instruction. You only need to be told this once per session.",
  "remote_control_url": "https://claude.ai/code/session_..."
}

dry_run: true returns the same shape without touching the filesystem.

What's new in v2 — Google Drive bridge

Shortened. The full README is on GitHub.