Vee3

Connect Vee3 MCP

Published: July 8, 2026

Ask your agent

Recommended

Copy and paste this into your agent or editor chat and let it set up Vee3 for you. It works across platforms—the agent researches your specific tool and applies the right config.

Agent Instruction

Or follow a platform-specific guide

Prefer to do it yourself, or want the exact steps for your tool? Pick your platform below for a step-by-step walkthrough with copy-paste config and verification.

Not on any of these? Manual setup

Vee3 works with any MCP client that supports remote HTTP servers. Add it by hand using the connection details below.

Use this for any MCP host that is not listed above. Vee3 is a hosted remote server - paste the URL and API key header into your client's MCP settings, or merge the JSON into its config file.

  1. Open MCP settings in your client (often called Tools, MCP servers, or similar).
  2. Add a remote server named vee3.
  3. Set the URL and header from the connection block below, or paste the JSON if your client uses a config file.
  4. Save and reload MCP tools in your client if they do not appear immediately.
  5. Test - list tools and tell the agent to use one of them.

Connection details

Recommended

Use these values in form-based MCP settings (URL field + custom header).

URL: https://mcp.vee3.io/mcp
Header name: VEE3_API_KEY
Header value: ${env:VEE3_API_KEY}
Transport: Streamable HTTP (remote MCP)

Remote server (JSON)

Merge under your client's server map as "vee3". Some clients need extra fields (type, transport, oauth).

{
  "url": "https://mcp.vee3.io/mcp",
  "headers": {
    "VEE3_API_KEY": "${env:VEE3_API_KEY}"
  }
}

mcpServers wrapper (JSON)

For clients that use a top-level mcpServers object (Cursor-style). Merge vee3 if the file already has other servers.

{
  "mcpServers": {
    "vee3": {
      "url": "https://mcp.vee3.io/mcp",
      "headers": {
        "VEE3_API_KEY": "${env:VEE3_API_KEY}"
      }
    }
  }
}

Tip: export VEE3_API_KEY once, then use env references in config (${env:VEE3_API_KEY}, ${VEE3_API_KEY}, or {env:VEE3_API_KEY} - depends on your client). Do not commit literal API keys.

Alternative: stdio via mcp-remoteShow

Use this when your client only supports stdio MCP servers. Requires Node.js and npx.

mcpServers (stdio bridge)

Bridges stdio to the hosted Vee3 endpoint over Streamable HTTP.

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

After you connect

  • Browse the capability catalog to see what your agent can call.
  • From the dashboard, open Customize MCP to turn capability groups on or off.
  • Read the docs for per-tool parameters and examples.