claude-duet-bridge
Related Servers
Alternatives to claude-duet-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceMCP server that routes Claude Desktop chat into Claude Code, enabling headless execution and terminal handoff with session continuity.4MIT
- AlicenseNot gradedqualityFmaintenanceThe self-hosted MCP bridge between Claude Chat and Claude Code.46AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceDeploy a remote MCP server on Cloudflare Workers without authentication. Enables custom tools and connections to MCP clients like Claude Desktop and Cloudflare AI Playground.-
- AlicenseAqualityDmaintenanceAn MCP server that connects Claude Desktop to an interactive Claude Code session running in a tmux terminal.1MIT
- FlicenseNot gradedqualityCmaintenanceA remote MCP server deployed on Cloudflare Workers without authentication, enabling custom tool integration and connection to AI Playground or Claude Desktop.-
- AlicenseNot gradedqualityBmaintenanceCodeMCP — a secure, workspace-bound bridge between your machine and ChatGPT, Claude, or any AI agent.4MIT
This server cannot be deployed
TDQS
Scored across 13 tools
Most tools target distinct concepts, but the set has several near-neighbors: send_job vs send_message vs start_session all push instructions to Claude Code, and read_messages vs read_reports both drain a mailbox. The descriptions do draw the lines (one-shot read-only job vs persistent session vs free-form note), but an agent must read carefully to pick correctly.
Almost every tool follows a clean verb_noun pattern (get_job, list_jobs, send_job, cancel_job, start_session, end_session, read_reports, post_report). The only outlier is bridge_status, which inverts the pattern to noun_verb while its siblings use verbs.
Thirteen tools is well within the sweet spot and each maps to a concrete operation across the three sub-areas (jobs, sessions, mailbox). Nothing looks redundant or padded.
Full lifecycle is covered for jobs (send/list/get/cancel) and sessions (start/list/end/open), plus two-way messaging and a status overview. Minor gaps exist: no way to fetch a single session's detail, no way to re-read already-consumed messages/reports explicitly addressed to one item, and no cleanup/purge for old jobs.