opencode-cc-tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENCODE_CC_TOOL_STATE_DIR | No | Override the state directory. Default is ~/.opencode-cc-tool |
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 |
|---|---|
| opencode_dispatchA | Start an |
| opencode_cancelA | Stop a running task: sends SIGTERM to the task's whole process group (opencode and any subprocess it spawned), escalating to SIGKILL after a grace period if it hasn't exited. A finished task's status is unaffected and returns a note instead of an error. Poll opencode_status afterward; the task moves to status 'cancelled' once its exit event lands. |
| opencode_waitA | Block on a running task's real exit event (or a timeout, whichever comes first) and return its status once settled. The closest analog to the built-in Agent tool's auto-resume behavior available over plain MCP request/response, without a poll loop. Capped internally at 45s so the call returns cleanly instead of hitting Claude Code's own MCP tool-call timeout; if status is still 'running' when it returns, call opencode_wait again. |
| opencode_statusA | Return structured status for a dispatched task: running | done | crashed | cancelled | unknown, plus exit code and log path once finished. Backed by the child process's real exit event, not log string-matching. |
| opencode_resultA | Return the final assistant message and metadata (tokens, cost, session id) for a finished task, parsed from opencode's own --format json event stream. |
| opencode_listA | List all known tasks (this server process's lifetime) with their statuses, newest first. |
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 6 tools
Each tool has a unique, well-defined purpose: dispatch starts tasks, cancel stops them, list enumerates tasks, status checks state, result retrieves output, and wait blocks for completion. No overlaps.
All tools follow a consistent pattern: 'opencode_' prefix followed by a verb (cancel, dispatch, list, result, status, wait). No mixing of styles.
Six tools cover the essential operations for managing opencode tasks without unnecessary bloat or gaps. The number is appropriate for the server's purpose.
The tool set provides complete lifecycle coverage for opencode tasks: create (dispatch), read (list, status, result), delete (cancel), and a blocking wait. No obvious missing operations.