Skip to main content
OpenCode reads MCP server definitions from a JSON config file. It uses "environment" (not "env") and expects "command" as an array.

​
File location

Project-scoped — create opencode.json in your project root: 
./opencode.json
Global — applies to every project on your machine: 
~/.config/opencode/opencode.json
Project config takes precedence over global config.

​
Config

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "versuno": {
      "type": "local",
      "command": ["npx", "-y", "versuno-mcp"],
      "environment": {
        "VERSUNO_API_KEY": "uk_live_xxx"
      }
    }
  }
}

​
Remote (hosted HTTP)

To use Versuno’s hosted server instead of npx, use the remote type with your key as a bearer token: 
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "versuno": {
      "type": "remote",
      "url": "https://mcp.versuno.ai/mcp",
      "headers": {
        "Authorization": "Bearer uk_live_xxx"
      },
      "enabled": true
    }
  }
}
The hosted server provides the read/query tools only — pull_asset and push_asset need local disk access, so use the local config above for those.

​
Enabling the server

OpenCode picks up config changes on the next session start. Run opencode in your terminal — it will spawn versuno-mcp automatically. To confirm the server loaded, check the tool list at startup or run: 
opencode --tools
You should see the five Versuno tools listed.

​
Using it

Reference your assets in any OpenCode prompt:
“Search Versuno for skill assets related to code review and apply the top result.”
OpenCode will call the appropriate MCP tool. See Security for permission settings.

​
Troubleshooting

If the server fails to start, OpenCode surfaces the stderr output in its error panel. The most common issues are a missing or invalid API key. See Troubleshooting.