Skip to main content
Glama
Sign In
opencode-http-mcp

opencode-http-mcp

by xuanpass
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to opencode-http-mcp

No user-submitted related servers found.

    Related Servers

    • opencode-mcp

      Wood535
      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 work — asking questions, implementing features, monitoring background jobs, answering prompts and permission requests, and reviewing changes across multiple projects. Supports synchronous runs, asynchronous jobs with polling and recovery, multi-project directory scoping, and configurable server authentication and tool profiles.
      25,826 npm
      MIT

    • opencode-mcp

      Mateusz64564
      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 ask questions, implement features, run background coding jobs, answer permission and question prompts, and review changes across multiple projects. It also exposes project-aware resources, prompts, and job monitoring tools with configurable provider and model defaults.
      25,826 npm
      MIT

    • opencode-mcp

      thierry67883
      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,826 npm
      MIT

    • opencode-mcp

      kobayashi0923
      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 ask questions, start and monitor background coding jobs, answer prompts and permission requests, and review changes across projects. It also exposes setup, model selection, job recovery, and configuration tools, along with resources and prompts, for multi-project workflows.
      25,826 npm
      MIT

    • opencode-mcp

      KhalidBradley77565
      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,826 npm
      MIT

    • opencode-mcp

      Hara673
      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 ask coding questions, implement features, run and monitor background jobs, answer prompts and permission requests, and review changes across multiple projects. Supports setup, provider/model selection, job recovery, and structured results with configurable tool profiles.
      25,826 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

    C2.6/5.0

    Scored across 85 tools

    Disambiguation2/5

    Several tools overlap heavily in purpose: opencode_message_send, opencode_message_send_async, opencode_ask, opencode_reply, opencode_run, and opencode_fire all send prompts or tasks, while opencode_check, opencode_wait, opencode_job_get, opencode_session_status, opencode_sessions_overview, and opencode_status all observe session/task status. The boundaries between these are unclear, leading to likely misselection.

    Naming Consistency3/5

    All tools share the opencode_ prefix and use snake_case, which helps, but the naming pattern is mixed: many follow resource_action (opencode_session_list, opencode_message_get) while others are bare verbs or nouns (opencode_ask, opencode_check, opencode_reply, opencode_run, opencode_fire, opencode_wait). This inconsistency makes the set less predictable.

    Tool Count1/5

    85 tools is an extreme mismatch for a single MCP server. Even though the domain is broad (sessions, messages, providers, TUI, etc.), this count far exceeds what an agent can manage, and many tools are redundant or niche, suggesting the surface should be split.

    Completeness4/5

    The server covers a wide range of operations (session lifecycle, messaging, config, providers, projects, VCS, agents, TUI, events, questions). However, notable gaps exist: there is no direct file write/edit tool (only read/list/status), and several find tools (opencode_find_text, opencode_find_file, opencode_find_symbol) are marked unavailable on 2.x.

    Resources