Sequential Thinking MCP Server
Dynamic problem-solving through sequential thought chains
Pipes Claude Code session output into Claude Chat — no more copy-paste between tools
{
"mcpServers": {
"io-github-rahuljava2807-claude-bridge-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Pipes Claude Code session output into Claude Chat — no more copy-paste between tools
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 0 days ago. 1 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationNo known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
The official Python SDK for Model Context Protocol servers and clients
An open-source AI agent that brings the power of Gemini directly into your terminal.
MCP Security Weekly
Get CVE alerts and security updates for io.github.rahuljava2807/claude-bridge-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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/<project-hash>/ 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.
get_latest_output — grab the most recent assistant message from any (or the most-recent) Claude Code session.list_sessions — enumerate all local sessions with project path, message count, and timestamps.get_session_context — fetch the last N messages from a session for context injection.watch_session — poll a session file every 2 seconds and drain new messages on demand.write_context (v2) — snapshot the last N messages into ~/.claude/bridge-context.md and ~/Documents/claude-bridge-context.md as clean markdown.start_auto_sync (v2) — keep that markdown snapshot live: rewrites both files every 30 seconds (configurable) so a synced folder stays current without manual calls.setup_drive_sync (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.send_to_session (v2.2) — queue a prompt for a specific Claude Code session via a cooperative inbox at ~/.claude/bridge-inbox/<session_id>.txt. Closes the read-only gap: Projects Claude → inbox → Claude Code acts on it.send_to_session (cooperative dispatch)v1 read sessions. v2 wrote context out to Drive. v2.2 lets the other side push prompts back in.
send_to_session overwrites ~/.claude/bridge-inbox/<session_id>.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 send_to_session 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.
Claude **Pr