Claude-Opencode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | Python path to the source directory, e.g. 'src'. | |
| DEFAULT_IDE | No | Preferred execution environment: 'cli_direct', 'vs_code', or 'antigravity'. | cli_direct |
| VSCODE_PATH | No | Path to the VS Code executable (code.cmd or code.exe). Overrides PATH lookup. | |
| OPENCODE_PATH | No | Path to the OpenCode CLI executable (opencode, opencode.cmd, or opencode.exe). Overrides PATH lookup. | |
| ANTIGRAVITY_PATH | No | Path to the Antigravity IDE executable (antigravity-ide.cmd). Overrides PATH lookup. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delegate_to_opencodeA | Delegate a real-time software engineering instruction to OpenCode CLI. Claude Desktop acts as the Planner and Architect. OpenCode CLI acts as the Coding Engineer. The dynamic prompt is forwarded unchanged to OpenCode executing in the target workspace. Args: prompt: Dynamic, real-time natural language engineering instruction generated by Claude. workspace_path: Absolute or relative local workspace directory path. ide: Optional IDE environment preference ('vs_code', 'antigravity', or 'cli_direct'). |
| continue_opencodeA | Continue an active OpenCode engineering session while preserving session context. Use this tool to send follow-up instructions, fix build/test failures, or proceed to the next engineering task in the development loop. Args: interaction_id: The OpenCode session ID of the previous interaction session to continue. prompt: Dynamic follow-up instruction generated by Claude Desktop. workspace_path: Local workspace directory path. ide: Optional IDE environment preference ('vs_code', 'antigravity', or 'cli_direct'). |
| open_workspace_in_ideB | Open an existing workspace directory in VS Code or Antigravity IDE. Args: workspace_path: Directory path of the workspace to open. ide: Target IDE ('vs_code' or 'antigravity'). Defaults to configured default IDE. |
| get_opencode_statusA | Check OpenCode CLI executable availability, version, and IDE readiness. |
| delegate_to_antigravityC | Alias for delegate_to_opencode. |
| ask_antigravityD | Alias for delegate_to_opencode. |
| continue_antigravityD | Alias for continue_opencode. |
| get_antigravity_statusB | Alias for get_opencode_status. |
| open_antigravity_workspaceC | Alias for open_workspace_in_ide with Antigravity IDE. |
| get_antigravity_workspaceB | Query currently active workspaces in local IDE. |
| inspect_antigravity_workspaceC | Inspect local workspace directory structure and manifest files. |
| read_antigravity_workspace_fileC | Safely read content of a workspace file. |
| diagnose_antigravity_workspaceC | Run project diagnostics in local workspace. |
| fix_antigravity_workspaceC | Apply targeted file write within workspace boundary. |
| launch_antigravity_workspaceC | Launch application in workspace using detected launcher. |
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 15 tools
Several tools are explicit aliases for the same operation, such as delegate_to_opencode/delegate_to_antigravity/ask_antigravity, get_opencode_status/get_antigravity_status, continue_opencode/continue_antigravity, and open_workspace_in_ide/open_antigravity_workspace. This creates serious ambiguity because an agent can select multiple different tool names to perform the same action, and the remaining antigravity workspace tools also have overlapping file/diagnostic boundaries.
There is no consistent naming pattern across the set: some tools use verb_to_target like delegate_to_opencode, others are target-prefixed like get_antigravity_status, and others are generic like open_workspace_in_ide. Aliases also have divergent names such as ask_antigravity, making the convention even less predictable.
15 tools is on the higher side for a single integration server, and the presence of at least five aliases makes the count feel padded rather than purposeful. However, once aliases are removed, the remaining unique session and workspace operations are roughly reasonable for the stated scope.
The core workflow of delegating to OpenCode, continuing sessions, checking status, opening workspaces, inspecting files, and running diagnostics is well covered. Minor gaps such as no session listing or cancellation can be worked around using returned interaction IDs and workspace queries.