{"id":"alaeddinemessadi-opencode-mcp","name":"opencode-mcp","af_score":62.5,"security_score":51.0,"reliability_score":28.8,"what_it_does":"opencode-mcp is an MCP server that bridges MCP clients (via stdio) to the OpenCode headless API over HTTP. It auto-starts an OpenCode server when needed and exposes 79 tools, 10 resources, and 6 prompts for delegating coding, debugging, and project/session operations.","best_when":"You have an MCP-capable coding assistant and want one consistent tool surface to control OpenCode sessions across multiple projects/directories.","avoid_when":"You cannot control or secure access to the local OpenCode server / auto-start process, or you need explicit, documented rate limit and retry/idempotency semantics for safe automation.","last_evaluated":"2026-03-30T15:35:17.868693+00:00","has_mcp":true,"has_api":false,"auth_methods":["HTTP basic auth to the OpenCode server (OPENCODE_SERVER_USERNAME/OPENCODE_SERVER_PASSWORD)","Provider/auth handled by the downstream OpenCode server (tooling includes Provider & Auth tools, but exact auth mechanism for OpenCode is not detailed here)"],"has_free_tier":false,"known_gotchas":["Auto-start behavior: the server may start opencode serve automatically if not running (OPENCODE_AUTO_SERVE=true by default), which can be surprising in locked-down environments.","Stateful sessions: prefer workflow tools (setup/run/wait/check) to maintain consistent session state; mixing fire/run/reply without sessionId tracking can lead to confusing outcomes.","Directory targeting: tools accept an optional directory for multi-project support; ensure the correct path is provided to avoid modifying the wrong project.","Error semantics: no explicit standardized error codes/retry guidance described in the provided content; agents should be prepared for upstream HTTP/API errors from OpenCode."],"error_quality":0.0}