Skip to main content
Glama
codex-mcp-opencode

codex-mcp-opencode

Related Servers

Alternatives to codex-mcp-opencode

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP bridge that lets ChatGPT chat mode operate the user's own computer, running project, file, and shell tasks through a local executor and returning progress and results to the conversation. It also coordinates Codex sessions (persistent or one-off) and other agent CLIs as sub-agents.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP clients such as Claude, Cursor, and VS Code to OpenCode's headless API so they can delegate coding work across projects — asking questions, implementing features, launching and monitoring background jobs, responding to permission and input requests, and reviewing the resulting changes. It supports multi-project directories, configurable default provider/model pairs, and both synchronous and asynchronous task workflows.
      25,387 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP clients such as Claude, Cursor, and VS Code to an OpenCode server's headless API so coding work can be delegated, answered, and monitored. It supports asking questions, launching foreground or background jobs, supplying required input and permissions, and reviewing resulting changes across projects.
      25,387 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP clients such as Claude, Cursor, and VS Code to OpenCode's headless API so users can delegate coding tasks, ask questions, run work in the background, and resolve permission or input requests across projects. It also supports monitoring job progress, reviewing resulting changes, and inspecting conversation history.
      25,387 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: configure handles defaults and model listing, run executes one-off tasks, run_task manages durable tasks, and sessions manages session lifecycle. No overlap.

    Naming Consistency4/5

    All tools use the 'opencode.' prefix and are lower case, but 'run_task' uses an underscore while others are single words, introducing minor inconsistency.

    Tool Count5/5

    With 4 tools, the set is well-scoped for managing OpenCode sessions and tasks—neither too few nor too many.

    Completeness4/5

    Covers core operations (configure, run, durable run, session management). Minor gaps like explicit task output retrieval or model listing beyond configure are present but not critical.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues