claude_code
Related Servers
Alternatives to claude_code
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.9MIT
- AlicenseAqualityDmaintenanceEnables Codex to delegate coding tasks to an OpenCode CLI locally, returning structured results such as exit codes, session summaries, tool calls, and git diffs.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to hand off coding tasks to a locally running DeepSeek Harness Desktop Host over MCP, reusing the Host's configured model and runtime and returning a session ID for status checks, incremental event streaming, waiting, and cancellation.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude Code to delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions that resume across calls.12 npmMIT
- AlicenseAqualityBmaintenanceEnables an MCP-capable coding client to list and read Codex sessions, resume or fork them, delegate persistent background coding tasks, and invoke Codex-configured models directly.81MIT
- FlicenseCqualityCmaintenanceEnables Codex to delegate already-scoped coding tasks to Claude Code and manage the resulting execution and fresh read-only review sessions, returning deterministic PASS/FAIL results through a local MCP interface.723-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose (headless Claude Code execution) is stated clearly and unambiguously.
With a single tool named claude_run, there is no opportunity for convention mixing. The name is readable and follows a noun_verb pattern that fits the server's identity.
A single blocking run tool is a thin surface for a coding-agent server; there is no way to list runs, check status, or cancel. It is defensible for a minimal wrapper but leaves the server feeling under-scoped.
The tool blocks until completion, so there is no async execution, status polling, cancellation, or output streaming. For long-running code edits and command execution these are significant gaps that will cause agent timeouts or dead ends.