Skip to main content
Glama
jdsalasca

mcp-opencode

by jdsalasca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-opencode

No user-submitted related servers found.

    Related Servers

    • TaskQuay

      lxjmaster
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT conversations to directly inspect local workspaces and delegate coding tasks to a local Codex agent, with controlled concurrency, reusable sessions, and task/usage tracking.
      1,205 npm
      MIT

    • local-agent-mcp

      ezra-y
      A
      license
      B
      quality
      C
      maintenance
      Enables ChatGPT to work directly on local projects by reading files, editing code, running tests and commands, inspecting Git state, and managing durable workflows, with optional delegation to local Codex agents for complex tasks.
      28
      MIT

    • codex-mcp-opencode

      Ichikawashadow
      A
      license
      A
      quality
      B
      maintenance
      A project-local MCP bridge that allows Codex Desktop to plan tasks and OpenCode to execute them within the current project directory, with session reuse and native OpenCode background subagents.
      4
      1
      MIT

    • chatgpt-with-codex

      yuumiqwq
      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

    • Core

      shadorig
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets ChatGPT work directly on a local project by reading and editing files, running shell commands and tests, keeping terminals open, and using the user's desktop, all paired with an approved workspace folder. It also splits independent jobs across persistent workers that retain context, while riding the user's existing ChatGPT plan rather than Codex quota.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 25 tools

    Disambiguation3/5

    Many tools have overlapping purposes, especially status/check/review which all inspect sessions and diffs. However, descriptions attempt to differentiate in specific ways, and the rest are more distinct.

    Naming Consistency4/5

    All tools share the consistent 'opencode_' prefix, but the suffix mixes verbs (run, fire, wait) and nouns (sessions, projects) without a strict verb_noun pattern. Still, the pattern is predictable and readable.

    Tool Count3/5

    At 25 tools, the server is on the heavy side for its scope. Several tools could likely be consolidated (e.g., status-like queries), but the count is not unreasonable for a full-featured session manager.

    Completeness4/5

    The tool set covers session lifecycle well: create, run, reply, fork, wait, abort, and monitor. Gaps include no explicit session deletion or update of provider configurations, but core workflows are present.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources