Connect Vee3 MCP to OpenCode

Published: July 8, 2026

Ask your agent

Recommended

Copy 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

Recommended

Uses {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}"
      }
    }
  }
}
  1. Open or create ~/.config/opencode/opencode.json for all projects, or opencode.json in a project root.
  2. Paste the config from above.
    • New file: paste the whole JSON object.
    • Already has servers: add only the vee3 entry inside the existing mcp object - keep other top-level keys (e.g. agent, tools) unchanged.
  3. Save the file and start a new OpenCode session if needed.
  4. Verify with opencode mcp list - vee3 should appear.
  5. Test in chat, e.g. “Capture a screenshot of https://example.com”.
Setup via CLI (interactive)Show

Run in your terminal:

opencode mcp add
  1. Choose remote
  2. Name: vee3
  3. URL: https://mcp.vee3.io/mcp
  4. Add header VEE3_API_KEY with your key (or edit the saved file to use {env:VEE3_API_KEY} and set oauth to false if 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