Skip to main content
Glama
anhnguyen0905

codex-mcp

by anhnguyen0905
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-mcp

No user-submitted related servers found.

    Related Servers

    • codex-mcp-server

      tuannvm
      A
      license
      A
      quality
      D
      maintenance
      Bridges Claude and OpenAI's Codex CLI for AI-powered code analysis, generation, and review, with support for session management, web search, and structured output.
      6
      687 npm
      645
      ISC

    • Codex MCP Server

      cexll
      A
      license
      C
      quality
      F
      maintenance
      Connects AI assistants like Claude to the Codex CLI for code analysis, editing, and execution. Supports file references with @ syntax, sandboxed code execution with approval workflows, and structured code changes for automated refactoring and documentation.
      8
      93 npm
      177
      MIT

    • codex-bridge-mcp

      WeiqiZhou2002
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables two-way collaboration between Claude Code and the Codex CLI: Claude can hand off plans for execution or adversarial review, while the working agent can block to ask Claude questions, report progress or findings, and receive mid-run corrections. Supports multiple named, resumable sessions per project with configurable model, effort, and sandbox settings.
      MIT

    • harness-bridge

      rbutera
      A
      license
      A
      quality
      A
      maintenance
      Bridges Claude Code and OpenAI Codex through MCP, allowing cross-harness querying, code review, explanation, and implementation delegation.
      6
      3 npm
      1
      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

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: discovering sessions, executing new tasks, resuming sessions, reviewing changes, batching work, reading metrics, and checking health. Though execute and batch both run Codex, their scope (single vs. fanned-out) is explicit and easy to distinguish.

    Naming Consistency4/5

    All tools share the consistent codex_ prefix and snake_case style, which makes them predictable. However, the suffix mixes verbs (execute, continue) with nouns (sessions, metrics, batch, health), so it is not a strict verb_noun convention.

    Tool Count5/5

    Seven tools is well-scoped for a Codex-focused server. Each tool covers a meaningful workflow: session discovery, execution, continuation, review, batch processing, metrics, and health checks, with no obvious bloat.

    Completeness4/5

    The set covers the core Codex lifecycle: create and run sessions, resume them, review changes, batch tasks, and observe usage/health. Minor gaps exist, such as no explicit tool for full session transcripts or canceling in-progress sessions, but agents can work around these using returned sessionIds and the CLI.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources