Skip to main content
Glama
codex-mcp-tool

codex-mcp-tool

Related Servers

Alternatives to codex-mcp-tool

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server wrapping the Cursor CLI agent, enabling Claude Code and other MCP clients to delegate tasks to Cursor's AI agent for file writing, bash commands, and codebase queries.
      -
    • A
      license
      B
      quality
      C
      maintenance
      An open-source MCP server that connects your IDE or AI assistant to the Codex CLI, enabling non-interactive automation with codex exec, safe sandboxed edits with approvals, and large-scale code analysis via @ file references.
      10
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.
      24 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that lets Claude Code or any MCP client delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions and tools for diffing and pushing changes.
      12 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that integrates Codex CLI into Claude Code workflows for code writing, execution, and review with session management. It features real-time progress monitoring via a local HTTP dashboard and supports detailed configuration for various coding tools.
      6
      13 npm
      167
      MIT

    TDQS

    B3/5.0

    Scored across 13 tools

    Disambiguation3/5

    ask-codex, do-act, batch-codex, and brainstorm all ultimately wrap the same Codex CLI execution, differentiated mainly by prompt framing and verification loops rather than distinct resources. review-changes is close to ask-codex as well, since a review is just a specialized Codex invocation. The descriptions do help separate single-task, batch, act-check-fix, and ideation modes, but an agent could easily pick the wrong wrapper.

    Naming Consistency3/5

    All names use kebab-case, which is good, but the conventions are mixed: verb_noun (ask-codex, list-skills, review-changes, fetch-chunk), bare nouns/utilities (health, version, help, ping), and modifier_noun (image-gen, batch-codex). do-act is vague compared to its siblings, and ask-codex vs batch-codex vs do-act do not read as a coherent family.

    Tool Count4/5

    13 tools is a well-scoped size for a CLI-wrapper server. A few slots are boilerplate (ping, help, version) rather than real capabilities, but overall each tool corresponds to a plausible use case.

    Completeness3/5

    Core execution paths are covered: single ask, batch, verified act, review, image generation, skills discovery, session listing, health, and chunk retrieval. However, sessions can only be listed/managed vaguely with no get/delete/detail tool, and there is no way to cancel or abort a long-running Codex run, which are common lifecycle gaps for this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data