DELETE_ME
Related Servers
Alternatives to DELETE_ME
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceBridges multiple CLI coding agents (Codex, Cursor, OpenCode, Claude, Antigravity) into any MCP client, enabling delegation of prompts, parallel execution, and code review workflows.60Mozilla Public 2.0
- AlicenseNot gradedqualityBmaintenanceRemote MCP coding bridge that gives ChatGPT/Codex secure local workspace access, including file retrieval, semantic code intelligence, Git, diagnostics, and guarded shell execution.25 npmMIT
- AlicenseNot gradedqualityFmaintenanceBridges the Model Context Protocol with Language Server Protocol to provide AI agents with persistent access to code intelligence features including navigation, diagnostics, refactoring, and completion across 7+ programming languages.2,705 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables LLM-powered code analysis, generation, debugging, and context management through MCP integration with IDEs like Cursor and Claude Desktop.MIT
- AlicenseBqualityBmaintenanceEnables MCP-compatible AI clients like Claude Code, Cursor, and Codex to invoke Google Antigravity's Gemini coding agent for repository-aware file operations, command execution, code review, test generation, and quota checks, while also providing a standalone dual-mode CLI.7MIT
- AlicenseNot gradedqualityCmaintenanceCodeMCP — a secure, workspace-bound bridge between your machine and ChatGPT, Claude, or any AI agent.3MIT
TDQS
Scored across 6 tools
The tools target distinct Codex usage modes: status, analysis, debugging, review, implementation, and consultation. However, codex_analyze, codex_consult, and codex_review_code have adjacent boundaries that could cause occasional misselection.
All tools use a consistent codex_ prefix and snake_case, which makes the set predictable. There is minor inconsistency between verb-only names (codex_analyze, codex_implement, codex_consult), verb_noun names (codex_debug_error, codex_review_code), and a noun name (codex_status).
Six tools is well-scoped for a Codex CLI wrapper, and each tool represents a meaningful, non-redundant operation. The count is neither thin nor bloated.
The surface covers common Codex interactions including status, analysis, debugging, review, implementation, and consultation. Minor gaps exist around applying changes, continuing sessions, or explicitly generating/running tests, but agents can work around these limitations.