Connect Vee3 MCP to OpenCode
Published: July 8, 2026
Ask your agent
RecommendedCopy and paste this into OpenCode chat and let the agent walk you through setup.
Agent Instruction
Connect to OpenCode
Add Vee3 as a remote MCP server in OpenCode's config. The copy block includes oauth: false so OpenCode uses your API key header instead of OAuth.
opencode.json
RecommendedUses {env:VEE3_API_KEY} - export that variable before starting OpenCode, or replace with your key.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vee3": {
"type": "remote",
"url": "https://mcp.vee3.io/mcp",
"enabled": true,
"oauth": false,
"headers": {
"VEE3_API_KEY": "{env:VEE3_API_KEY}"
}
}
}
}
- Open or create
~/.config/opencode/opencode.jsonfor all projects, oropencode.jsonin a project root. - Paste the config from above.
- New file: paste the whole JSON object.
- Already has servers: add only the
vee3entry inside the existingmcpobject - keep other top-level keys (e.g.agent,tools) unchanged.
- Save the file and start a new OpenCode session if needed.
- Verify with
opencode mcp list-vee3should appear. - Test in chat, e.g. “Capture a screenshot of https://example.com”.
Setup via CLI (interactive)ShowHide
Run in your terminal:
opencode mcp add- Choose remote
- Name:
vee3 - URL:
https://mcp.vee3.io/mcp - Add header
VEE3_API_KEYwith your key (or edit the saved file to use{env:VEE3_API_KEY}and setoauthtofalseif missing)
The CLI does not support a one-line install flag. Pasting into opencode.json is usually faster.
OpenCode uses {env:VEE3_API_KEY} (not ${env:…}). Do not commit literal API keys.
Verify the connection
Run opencode mcp list and confirm vee3 appears. Then ask the agent to call meta-tools.list_groups or search the catalog with meta-tools.search. Name vee3 explicitly in chat if tools do not show up unprompted.
Customize which tools appear
From the dashboard, open Customize MCP to turn capability groups on or off. Changes apply to your MCP server on the next connection.
Next steps
- Browse the capability catalog for what you can call.
- Read the docs for per-tool parameters and examples.