opencode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENCODE_BIN | No | opencode binary (absolute path recommended) | opencode |
| OPENCODE_AGENT | No | opencode agent forced on every run (e.g. explore) | |
| OPENCODE_REPOS_DIR | No | Where checkouts live | ~/codelab/repositories |
| ASK_CODEBASE_TIMEOUT | No | Hard timeout for the opencode run, in seconds | 600 |
| OPENCODE_MANIFEST_DIR | No | Directory of .opencode_mcp_manifest.json | ~ |
| OPENCODE_REPO_TTL_DAYS | No | Re-fetch a repo after this many days | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_codebaseA | Ask a natural-language question about a GitHub repository and get an answer grounded in the real code. READ-ONLY: never writes, edits, builds, or executes anything. The harness fetches the repo itself (clone or refresh, max every few days) — a nonexistent repo fails fast with the exact git error. Stateful PER REPOSITORY: continue_session=true resumes the latest discussion of that owner/repo (follow-up questions keep their context); false (default) starts a fresh one. Optional branch pins a specific branch. Use it for architecture questions, where a feature lives, request flow, conventions, design rationale, etc. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined as read-only codebase Q&A.
The single tool name 'ask_codebase' follows a clear verb_noun pattern, which is consistent and descriptive.
One tool feels thin for a general-purpose MCP server, but it is appropriately focused for a specialized read-only Q&A assistant. The count is borderline but acceptable.
The tool covers the entire stated domain of asking questions about a codebase, with session state, branch selection, and error handling. No obvious gaps for its intended purpose.