codex-codebuddy-mcp
Related Servers
Alternatives to codex-codebuddy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.4MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.994 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables Codex agents to discover projects, read existing conversation histories, and send messages to specific conversations across trusted machines using a lightweight local bridge over SSH.-
- FlicenseAqualityAmaintenanceEnables MCP clients to control the local Codex CLI, including running and resuming agent sessions, forking, code review, applying diffs, and generating images, with background execution for long-running tasks.18-
- AlicenseNot gradedqualityAmaintenanceLets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.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
TDQS
Scored across 5 tools
Each tool targets a clearly distinct action: session creation, session teardown, sending a prompt, resolving a permission request, and cancelling a turn. There is no overlap or ambiguity between these operations.
All tool names follow a predictable snake_case verb_noun pattern: create_, close_, prompt_, respond_, cancel_. The shared 'codebuddy' anchor makes the set easy to scan and understand.
Five tools cover the full interaction lifecycle without redundancy. Each tool corresponds to a distinct phase of using a CodeBuddy session, so the count is well-scoped for the server's purpose.
The tool surface covers the complete workflow: create a session, prompt it, handle permission requests, cancel turns, and close the session. There are no obvious dead ends or missing operations needed for the advertised functionality.