Skip to main content
Glama
tksfjt1024

codex-cli-mcp-slim

by tksfjt1024
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to codex-cli-mcp-slim

No user-submitted related servers found.

    Related Servers

    • codex-app-mcp

      abetoots
      F
      license
      A
      quality
      B
      maintenance
      Enables 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.
      2
      -

    • codex-mcp

      alvarosw
      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
      6 npm
      MIT

    • mcp-server-codex

      jmorille
      F
      license
      A
      quality
      A
      maintenance
      Enables 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.
      18
      -

    • 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
      1,102 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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources