codex-local-mcp
Related Servers
Alternatives to codex-local-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT conversations to directly inspect local workspaces and delegate coding tasks to a local Codex agent, with controlled concurrency, reusable sessions, and task/usage tracking.1,713 npmMIT
- 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
- AlicenseCqualityFmaintenanceConnects AI assistants like Claude to the Codex CLI for code analysis, editing, and execution. Supports file references with @ syntax, sandboxed code execution with approval workflows, and structured code changes for automated refactoring and documentation.8172 npm179MIT
- FlicenseNot gradedqualityBmaintenanceEnables external AI (ChatGPT, Claude) to securely access a local workspace via Cloudflare Tunnel, providing file operations, shell commands, Git operations, and more with bearer token authentication and sandbox isolation.1-
- AlicenseAqualityCmaintenanceEnables 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
- FlicenseBqualityDmaintenanceConnects AI assistants to a local Codex engine for performing deep, project-level code reviews and automated refactoring. It enables context-aware bug fixes and multi-file analysis through a standardized bridge between modern AI clients and local development environments.42-
TDQS
Scored across 3 tools
The three tools are largely distinct: one executes a coding agent, one reads artifact files, and one generates images. The only minor ambiguity is that codex_run's general-purpose mandate could conceptually cover image generation, but the dedicated image tool helps agents choose correctly.
All tools share a codex_ prefix and verb-first names (run, read_artifact, generate_image), which is a clear and predictable pattern. codex_run is slightly less descriptive because it omits a noun object, but it does not break the style badly enough to warrant a lower score.
Three tools is appropriate for a narrow local-Codex wrapper: each tool covers a distinct operation and none feels redundant or missing. The count is well within the ideal 3-15 range for a focused MCP server.
The server covers the core workflow of running a Codex task, inspecting generated artifacts, and generating images. Minor gaps remain, such as no explicit workspace listing, cancellation, or status operations, but agents can accomplish the primary goals with this surface.