Skip to main content
Glama
nayagamez

codex-cli-mcp

by nayagamez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-cli-mcp

No user-submitted related servers found.

    Related Servers

    • codex-mcp-go

      w31r4
      A
      license
      Not graded
      quality
      D
      maintenance
      Wraps OpenAI's Codex CLI as an MCP server, enabling AI clients like KiloCode, Roo Code, and Cline to leverage Codex for code generation, debugging, and analysis through natural language.
      52
      MIT

    • codex-mcp-server

      4dhxm
      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
      949 npm
      4
      Apache 2.0

    • codex-app-mcp

      PyYoshi
      A
      license
      Not graded
      quality
      B
      maintenance
      A 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: codex starts a new conversation, while codex-reply continues an existing one using a thread ID. There is no ambiguity between them, as each accepts different inputs and performs a different action.

    Naming Consistency4/5

    Both tool names share the 'codex' prefix, but 'codex' is a standalone verb while 'codex-reply' is a compound with a hyphen. This is a minor inconsistency, but the pattern is predictable and readable, clearly indicating the primary action and the continuation action.

    Tool Count3/5

    With only 2 tools, the set is on the low end of the range, but it is appropriate for the narrow scope of running Codex CLI sessions. The tools cover the essential start and continue operations, though the set feels thin compared to more comprehensive servers.

    Completeness4/5

    The core lifecycle of starting and continuing a conversation is covered, which covers the main use case. However, there are no tools for listing active threads, ending sessions, or retrieving session history, which are minor gaps given the focus on interactive coding tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources