opencode-http-mcp
Related Servers
Alternatives to opencode-http-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceConnects 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.22,031 npmMIT
- FlicenseAqualityAmaintenanceAn MCP server that provides OpenCode's native tools (file read/write/edit, search, shell, web fetch/search, and more) to compatible Code CLIs like Codex and Claude Code.11282 npm-
- AlicenseNot gradedqualityAmaintenanceConnects MCP clients such as Claude, Cursor, and VS Code to OpenCode's headless API, enabling users to ask questions, implement features, monitor background work, respond to questions and permissions, and review changes across projects.22,031 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.2MIT
- AlicenseCqualityFmaintenanceThis MCP server gives an AI coding host controlled, client-agnostic access to a local machine's developer capabilities: transactional file edits, shell and PTY execution, Git and project inspection, language-server operations, isolated browser automation, Windows UI automation, VS Code state, durable jobs, and checkpoints, all bounded by filesystem root allowlisting and resource admission controls. It speaks standard MCP over stdio, Streamable HTTP, and legacy HTTP+SSE, and can also run headless as a long-lived job runner without any hosted model vendor.114ISC

GenieOS MCP Serverofficial
AlicenseAqualityCmaintenanceStdio bridge for editors to connect to the GenieOS MCP server, enabling AI agents to interact with GenieOS via Streamable HTTP transport.649 npmMIT
TDQS
Scored across 85 tools
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.
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.
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.
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.