Skip to main content
Glama
4714407

codex-app-server-mcp

by 4714407
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to codex-app-server-mcp

No user-submitted related servers found.

    Related Servers

    • codex-app-mcp

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

    • codex-app-server-mcp

      Goudu666
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code or any MCP client to delegate hands-on coding work to OpenAI Codex over a persistent app-server process, keeping long-lived threads with follow-ups, async polling, approvals, steering, and interrupts. Supports native code review, resuming existing sessions, structured output, and parallel worktree-isolated tasks.
      10
      24 npm
      1
      MIT

    • codex-mcp

      sulin314159-netizen
      A
      license
      Not graded
      quality
      C
      maintenance
      Wraps the Codex engine in a local stdio MCP server so any MCP-capable agent can run coding turns as tools, with blocking runs, start/poll progress, command approvals, interrupts, thread resume, and token usage. It also supports custom OpenAI-compatible providers, letting teams blocked by signup, payment, or network limits still use the engine.
      25 npm
      MIT

    • 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
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool maps to a distinct Codex operation: start, status, cancel, steer, review, compact, pending input, answer input, model listing, and diagnostics. Even similar actions like codex_steer and codex_answer_input are cleanly separated by their stated purpose.

    Naming Consistency4/5

    The codex_ prefix and snake_case style are consistent throughout, making the family easy to recognize. Minor deviations exist: codex_models and codex_status are noun-like rather than verb_noun, while most others follow an action-oriented pattern.

    Tool Count5/5

    Ten tools is a well-scoped set for managing Codex tasks and app-server operations. Each tool covers a meaningful lifecycle or capability without unnecessary redundancy.

    Completeness4/5

    The surface covers the main task lifecycle: start, monitor, cancel, steer, answer pending input, compact context, and review. Minor gaps exist around broader thread history or explicit thread deletion, but these are not essential for the core workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources