MCP-Claude Code Bridge
Related Servers
Alternatives to MCP-Claude Code Bridge
No user-submitted related servers found.
Related Servers
- FlicenseAqualityNot gradedmaintenanceBridges Claude Desktop, Claude Code CLI, and Claude Code for VS Code, enabling developers to plan in Desktop, save specs to project directories, and invoke Claude Code CLI with seamless state sharing across interfaces.4-
- AlicenseNot gradedqualityDmaintenanceConnects Claude Desktop and Claude Code, enabling autonomous exchange of messages, files, and code while keeping their context windows separate.4MIT
- AlicenseBqualityDmaintenanceExecutes development tasks by bridging Claude Desktop with Claude Code CLI, enabling automated code generation and task completion in specified working directories.82 npmMIT
- FlicenseNot gradedqualityDmaintenanceBridges Claude Desktop with a local RAG-powered code agent API, enabling context-aware codebase queries and conversation continuity.-
- AlicenseAqualityAmaintenanceBridges Claude Code and OpenAI Codex CLI for an interactive plan-execute-review workflow, enabling Claude to interview, design, and review while Codex implements code changes.7291 npm3MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Claude Desktop with Claude Code, allowing users to delegate tasks to Claude Code directly from Claude Desktop conversations, supporting both synchronous and background execution with session reuse.2 npmMIT
TDQS
Scored across 5 tools
Most tools have distinct purposes: claude_code_task for coding execution, create_project for project setup, list_files and read_file for file inspection, and run_command for shell operations. However, claude_code_task and run_command could potentially overlap if coding tasks involve shell commands, but their descriptions help differentiate them.
The naming is mixed: claude_code_task uses a descriptive compound name, while the others follow a verb_noun pattern (create_project, list_files, read_file, run_command). This inconsistency is noticeable but still readable, as most tools use clear verbs and nouns.
With 5 tools, the count is reasonable for a code bridge server, covering project creation, file operations, and command execution. It feels slightly thin for broader coding workflows, but each tool serves a clear purpose without obvious bloat.
The toolset covers basic project and file operations, but there are notable gaps for a code-focused domain: no tools for writing/modifying files, deleting files, or managing dependencies. This could limit agent workflows, though core inspection and execution are present.