Vee3

Connect Vee3 MCP to OpenClaw

Published: July 8, 2026

Ask your agent

Recommended

Copy and paste this into OpenClaw chat and let the agent walk you through setup.

Agent Instruction

Connect to OpenClaw

Add Vee3 under mcp.servers in OpenClaw config.

openclaw.json (streamable HTTP - recommended)

Recommended

Uses ${VEE3_API_KEY} - export that variable or add it to ~/.openclaw/.env.

{
  "mcp": {
    "servers": {
      "vee3": {
        "url": "https://mcp.vee3.io/mcp",
        "transport": "streamable-http",
        "headers": {
          "VEE3_API_KEY": "${VEE3_API_KEY}"
        }
      }
    }
  }
}
  1. Open or create~/.openclaw/openclaw.json
  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.servers object.
  3. Set your API key in headers, or add VEE3_API_KEY=vee3_live_... to ~/.openclaw/.env and keep ${VEE3_API_KEY} in the config.
  4. Save the file. OpenClaw hot-reloads config; start a new agent session if tools do not appear.
  5. Verify with openclaw mcp list and openclaw mcp show vee3.
  6. Test in a coding or messaging tool profile - MCP tools are hidden in minimal or when bundle-mcp is denied.
Setup via CLIShow

Writes the same server definition to config without connecting to Vee3:

openclaw mcp set

Run in bash or similar. On PowerShell, paste into openclaw.json instead.

openclaw mcp set vee3 '{"url":"https://mcp.vee3.io/mcp","transport":"streamable-http","headers":{"VEE3_API_KEY":"${VEE3_API_KEY}"}}'

Then run openclaw mcp list to confirm vee3 is registered.

Alternative: stdio via mcp-remoteShow

Use only if direct HTTP does not work. Requires Node.js and npx.

openclaw.json (stdio bridge)

Replace the vee3 HTTP entry with this stdio entry, or use it on a fresh file.

{
  "mcp": {
    "servers": {
      "vee3": {
        "command": "npx",
        "args": [
          "-y",
          "mcp-remote@latest",
          "https://mcp.vee3.io/mcp",
          "--header",
          "VEE3_API_KEY: ${VEE3_API_KEY}"
        ]
      }
    }
  }
}

OpenClaw uses ${VAR} env substitution (uppercase names only). Do not commit literal API keys.

Verify the connection

Run openclaw mcp list and confirm vee3 appears. Run openclaw mcp show vee3 to inspect the server definition. Then ask the agent to call meta-tools.list_groups or search the catalog with meta-tools.search. Use a coding or messaging tool profile—MCP tools are hidden in minimal or when bundle-mcp is denied.

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