codex-mcp-opencode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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.configureC | Lists OpenCode models and stores only bridge defaults. It never stores provider keys or edits project paths. |
| opencode.runB | Creates or resumes a project-local OpenCode session and executes a concise task. This may edit the current project. |
| opencode.run_taskA | Starts a durable OpenCode task when the MCP host negotiates task support. The task is recovered from the OpenCode session after MCP restart. |
| opencode.sessionsB | Lists, cancels, deletes, or cleans expired bridge-managed OpenCode sessions. Active and child sessions are protected from deletion. |
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 4 tools
Each tool has a clear, distinct purpose: configure handles defaults and model listing, run executes one-off tasks, run_task manages durable tasks, and sessions manages session lifecycle. No overlap.
All tools use the 'opencode.' prefix and are lower case, but 'run_task' uses an underscore while others are single words, introducing minor inconsistency.
With 4 tools, the set is well-scoped for managing OpenCode sessions and tasks—neither too few nor too many.
Covers core operations (configure, run, durable run, session management). Minor gaps like explicit task output retrieval or model listing beyond configure are present but not critical.