codex-dobby-mcp
Related Servers
Alternatives to codex-dobby-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that lets Claude Code delegate durable background tasks, reasoning profiles, thread resumption, and native image generation to your local Codex CLI.101MIT
- AlicenseAqualityBmaintenanceAn MCP server for running Claude Code and the Codex CLI as a pair: Claude drives, and hands self-contained tasks to Codex as background jobs.8MIT
- AlicenseAqualityBmaintenanceA local MCP server that lets Claude Code orchestrate Codex CLI and OpenCode CLI as sub-agents with strict security, concurrency, and output limits.41MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.13 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server enabling Claude to consult Codex (GPT-5.x) mid-task for second opinions, plan/diff review, brainstorming, and codebase exploration via structured debates and permission-controlled interactions.2MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables Claude to discover and delegate tasks to local Codex Skills and plugins, bridging Claude's natural language understanding with Codex's execution capabilities.Apache 2.0
TDQS
Scored across 11 tools
Each tool has a uniquely defined purpose with no overlap. brainstorming, building, planning, researching, reviewing, validating, and reverse-engineering are clearly distinct activities, and run-management tools are separate.
Most tools use a single verb (brainstorm, build, plan, etc.) while run-management tools use verb_noun pattern (start_run, get_run). This is mostly consistent with minor deviation.
11 tools is well-scoped for a code development assistant. Each tool serves a distinct phase or function without unnecessary duplication.
The tools cover the full lifecycle from idea evaluation (brainstorm), planning, implementation (build), review, validation, reverse engineering, and run management. No obvious gaps for the stated purpose.