Skip to main content
Glama

Related Servers

Alternatives to mcp-server-codex

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.
      9
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Grok Build to orchestrate the local Codex CLI for code reviews, adversarial reviews, task rescue, session transfer, and background job management through MCP tools.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to delegate coding tasks to a locally installed AI coding CLI over MCP, returning results, cost and turn metadata, and reusable session IDs for follow-up work.
      174 npm
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Bridges MCP clients with local Codex CLI to execute autonomous coding tasks, manage threads, and inspect history via SQLite state.
      13
      2,084 npm
      4
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: session lifecycle, job control, agent messaging, and preset management are all cleanly separated. Even the closely related codex_inbox, codex_reply, and codex_tell are easy to tell apart from their descriptions.

    Naming Consistency5/5

    All tools share a consistent codex_ prefix and snake_case format, with clear verb or noun segments following it. The naming is predictable enough that an agent can infer the role of an unfamiliar tool from the pattern.

    Tool Count4/5

    18 tools is slightly above the ideal compact range, but the count is justified by the multiple coherent clusters: sessions, jobs, inbox/reply messaging, presets, and code review. It feels organized rather than bloated.

    Completeness4/5

    The core lifecycle is well covered: start, resume, fork, list, monitor, cancel, and communicate with runs, plus full preset CRUD. Minor gaps exist, such as no explicit session deletion or a way to list all background jobs, but they do not block the main workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues