codex-cli-mcp-slim
Related Servers
Alternatives to codex-cli-mcp-slim
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to start new Codex conversations and continue existing threads, exposing codex and codex-reply tools over stdio via the Codex app-server protocol.2MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.96 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Code to use the latest Codex CLI as a tool, starting new Codex threads and continuing them with replies, including approvals handling and progress notifications. It keeps the classic codex and codex-reply tools working while letting users swap in newer Codex binaries to unlock the newest models.MIT
- AlicenseAqualityAmaintenanceEnables 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.18MIT
- AlicenseCqualityDmaintenanceBridges MCP clients with local Codex CLI to execute autonomous coding tasks, manage threads, and inspect history via SQLite state.13687 npm4Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA local stdio MCP server that lets any MCP client start a Codex thread and continue it by opaque thread ID through the codex and codex-reply tools, with fail-closed sandboxing and approval policies. It restores the removed Codex CLI MCP integration by bridging clients like OpenCode to the official Codex SDK.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: `codex` starts a non-interactive Codex session, while `codex-reply` resumes an existing session by THREAD_ID. Agents can easily choose between initial execution and continuation without overlap.
Both names share the `codex` prefix and use kebab-case, making the relationship obvious. However, the first tool is a bare noun while the second appends an action-like suffix, so it is not a uniform verb_noun convention.
Two tools is slightly under the typical 3-15 range, but for a deliberately slim CLI wrapper it is well-scoped. Each tool earns its place: one starts a session, one continues it.
The set covers the core Codex session lifecycle: start a session and continue it with a follow-up prompt. It lacks broader session management such as listing, cancelling, or checking status, but these are minor gaps given the slim wrapper scope.