Skip to main content
Glama
Codex to OpenCode MCP Server

Codex to OpenCode MCP Server

by TAO-MINGYU

Related Servers

Alternatives to Codex to OpenCode MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to delegate coding tasks to a locally installed AI coding CLI over MCP, returning results, cost and turn metadata, and reusable session IDs for follow-up work.
      174 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code, Codex CLI, and Cursor-agent to delegate bounded coding tasks to a local OpenCode v2.x installation via a single opencode_execute tool, returning the model's response, git diff/status summary, exit code, and session ID.
      1
      20 npm
      MIT
    • 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
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to delegate a bounded implementation task to the locally installed Claude Code CLI for scoped file edits and optional mechanical checks while keeping planning, review, and final decisions with Codex.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.
      MIT

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have clearly distinct roles: opencode_execute delegates a coding task, while opencode_check resolves the executable and reports its version. There is no realistic confusion between performing an action and checking the installation.

    Naming Consistency5/5

    Both tools use the same opencode_ prefix followed by a concise imperative verb, maintaining a consistent snake_case pattern. Though the prefix is a product name, the convention is uniform and predictable.

    Tool Count3/5

    Two tools is at the low end of typical server scope and feels thin for a coding integration. However, the narrow focus on delegating a single task plus a health check is reasonable enough to be borderline appropriate.

    Completeness4/5

    The server covers its core purpose: opencode_execute handles task delegation, and opencode_check verifies the underlying executable. Obvious lifecycle tools such as cancellation or querying current task status are absent, but they fall outside the stated minimal purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues