claude-desktop-to-code
Related Servers
Alternatives to claude-desktop-to-code
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityFmaintenanceThe self-hosted MCP bridge between Claude Chat and Claude Code.46AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceMCP server wrapping Claude CLI, enabling any MCP host like Cursor to use Claude as a sub-agent with dispatch modes.87 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that connects Claude Desktop to an interactive Claude Code session running in a tmux terminal.1MIT
- AlicenseAqualityCmaintenanceMCP server that lets Claude Code drive the local Codex CLI as a sub-agent for concurrent queries and optional file/shell actions, using the CLI's existing login and sessions.481 npm1MIT
- AlicenseAqualityCmaintenanceA minimal local MCP server that lets Claude Desktop or Claude Code delegate coding tasks to Grok Build running headless as a subagent.542 npm1MIT
TDQS
Scored across 4 tools
The three Claude Code-invoking tools (ask_claude_code, handoff_to_terminal, open_in_claude_code) share the same underlying target, but their descriptions clearly separate headless execution, continuing a session on screen, and opening a user-driven window. A small amount of overlap remains between handoff_to_terminal and open_in_claude_code since both surface a window, but the intent differences are spelled out.
All names are lowercase snake_case starting with a verb (list_, ask_, handoff_, open_), which is readable and predictable. The pattern varies slightly between verb_noun and verb_preposition_noun forms, but that maps onto meaning rather than being arbitrary.
Four tools is well-scoped for a bridge server that routes and hands off work to Claude Code. Each tool covers a distinct step in the workflow and none feels redundant or superfluous.
The surface covers profile discovery, headless execution, session continuation, and user-driven handoff, which is a coherent lifecycle. Minor gaps exist around session/state management (e.g., listing or managing existing sessions or profiles), but core workflows are reachable.