Skip to main content
Glama
jmorille

mcp-server-codex

by jmorille
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-server-codex

No user-submitted related servers found.

    Related Servers

    • 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
      MIT

    • pokeclaw

      madebydia
      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

    • codex

      jinxlzc
      A
      license
      Not graded
      quality
      C
      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

    • 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
      577 npm
      4
      Apache 2.0

    • Lumen Bridge

      diabetic0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients and external AI supervisors to oversee and steer native Codex sessions through a thin local stdio bridge. It exposes eleven codex_* supervisory tools for tasks such as listing threads, starting turns, observing progress, steering, responding to approvals, interrupting, checkpointing, and rolling over work.
      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

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct action: starting, resuming, forking, reviewing, applying, listing, image generation, and job management are clearly separated. The session-lifecycle tools (exec/resume/fork) and job tools (status/logs/cancel) have well-defined boundaries with explicit descriptions.

    Naming Consistency4/5

    All tools share the codex_ prefix and use lowercase snake_case, making the set predictable. The naming shifts slightly between verb-first (codex_exec, codex_list_sessions) and noun-first (codex_job_status, codex_job_logs), but the pattern remains readable and consistent in style.

    Tool Count5/5

    Ten tools is well-scoped for a Codex agent server covering session lifecycle, background jobs, code review/apply, and image generation. Each tool has a clear purpose and none feel redundant.

    Completeness4/5

    The core workflows are covered: start/resume/fork sessions, review and apply changes, manage background jobs, and list sessions. A few minor gaps exist, such as no explicit job listing or session deletion, but agents can work around these without major failures.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources