opencode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TOOL_TIMEOUT | No | Server-side maximum timeout for opencode_wait_for_task in milliseconds. Can be set via environment variable or CLI argument MCP_TOOL_TIMEOUT=<ms>. Defaults to 300000 (5 minutes). | 300000 |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| opencode_start_serverB | Start a headless OpenCode server instance in the current working directory |
| opencode_stop_serverB | Stop a running OpenCode server instance |
| opencode_list_agentsA | List agents (native and custom) and available models/providers on an OpenCode server instance |
| opencode_start_taskB | Delegate a task to an OpenCode agent: create a session and start the prompt without waiting for it to finish |
| opencode_get_task_statusB | Get the current status of a delegated task |
| opencode_get_task_resultB | Get the final result of a completed task |
| opencode_wait_for_taskA | Long-poll one or more delegated tasks until they finish or the timeout elapses. Use mode 'all' to wait for all tasks, or 'any' to return as soon as one completes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| delegate_task | Instructions for the correct workflow to delegate tasks to OpenCode agents via this MCP server |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action: server lifecycle (start/stop), task lifecycle (start, wait, get result, get status), and agent listing. No overlap or ambiguity.
All tools follow a consistent 'opencode_' prefix with verb_noun pattern (e.g., start_server, get_task_result). No mixing of conventions.
Seven tools cover core server and task management appropriately. Neither too sparse nor too bloated for the domain.
Covers server start/stop, agent listing, and task delegation with status/result retrieval. Missing a cancel_task or list_tasks tool, but core workflows are well-supported.