Skip to main content
Glama
NtTestAlert

cc-codex-mcp

by NtTestAlert
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cc-codex-mcp

No user-submitted related servers found.

    Related Servers

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

    • codex-subagent-mcp

      parisbs
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code to delegate coding tasks—investigation, review, long-running background jobs, and optional file edits—to a locally installed OpenAI Codex CLI, with the model and reasoning effort chosen per task and read-only execution by default. Follow-up requests reuse Codex's existing context, and write-enabled delegations can be confined to a managed git worktree so the user's own checkout stays untouched.
      8
      42 npm
      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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    codex_ask starts a new independent-review thread, while codex_followup continues an existing one via thread_id. The two purposes are cleanly separated with no overlapping scope, so an agent can choose reliably.

    Naming Consistency5/5

    Both tools use the same codex_ prefix with snake_case action suffixes (ask, followup). The pattern is predictable and no conventions are mixed.

    Tool Count4/5

    Two tools is lean but well-matched to a narrow purpose: initiate an opinion thread and extend it. It is slightly below the typical 3-15 range, but each tool clearly earns its place.

    Completeness4/5

    The ask/follow-up pair covers the core lifecycle of getting and continuing an independent review. Minor gaps such as listing or cancelling threads exist but are not required for the stated workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources