this is a little hack that I had Claude Code spin up for me and it only kinda half works. feel free to pirate it but don't expect much despite the fact that Claude Code does a great job of generating readmes that look like what you'd find in a finished product!
A Model Context Protocol (MCP) server that allows Claude Desktop to interface with Claude Code instances. This enables remote control and coordination between different Claude environments.
- 
Install dependencies:
npm install
 - 
Test the server:
npm start
 - 
Configure Claude Desktop: Add to your Claude Desktop MCP configuration (
~/Library/Application Support/Claude/claude_desktop_config.jsonon macOS):{ "mcpServers": { "claude-code-bridge": { "command": "node", "args": ["/absolute/path/to/this/project/src/index.js"] } } } 
- check_claude_code_installation: Verify Claude Code is available
 - execute_claude_code_command: Send commands to Claude Code
 - start_claude_code_session: Initialize a new Claude Code session
 - read_file_via_claude_code: Read files through Claude Code
 - write_file_via_claude_code: Write files through Claude Code
 
Once configured, you can use these tools in Claude Desktop:
Check if Claude Code is installed on the system
Start a new Claude Code session in /path/to/project and ask it to analyze the codebase
Execute command: "Create a new React component called UserProfile"
This is a basic implementation that demonstrates the concept. The server currently:
- Simulates Claude Code integration (since we're building without the actual CLI)
 - Provides a foundation for real integration once Claude Code CLI is available
 - Shows the MCP bridge pattern for inter-Claude communication
 
- Real Claude Code integration when CLI is available
 - Persistent session management
 - Bidirectional communication
 - Network MCP server version for remote access
 - Session state synchronization
 - Error handling and recovery
 
# Run in development mode with auto-reload
npm run devTo extend this to work with Claude.ai web/mobile, you'd:
- Add HTTP/WebSocket transport instead of stdio
 - Implement authentication/authorization
 - Add session management
 - Handle concurrent connections
 - Deploy as a network service
 
The MCP protocol already supports this - just swap the transport layer!