Vee3

Connect Vee3 MCP to Codex

Published: July 8, 2026

Ask your agent

Recommended

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

Agent Instruction

Connect to Codex

Run the command below in your terminal. Set VEE3_API_KEY in your shell or profile first - Codex reads that variable at runtime and sends it as a Bearer token (Vee3 accepts that). Restart Codex after running the command, then verify with codex mcp list.

Terminal command

Recommended

Recommended - registers hosted Vee3 MCP in ~/.codex/config.toml.

codex mcp add vee3 --url https://mcp.vee3.io/mcp --bearer-token-env-var VEE3_API_KEY

Codex chat may not mention MCP servers unprompted

In chat, a general “list available MCP servers” prompt may answer none even when vee3 is configured. Name the server explicitly - e.g. “Use the vee3 MCP server to capture a screenshot of example.com” or “List all tools from the vee3 MCP server”.

Manual setup via config.tomlShow
  1. Open ~/.codex/config.toml (or create it). For a single project, use .codex/config.toml in a trusted repo.
  2. Add the vee3 block under mcp_servers. Merge into existing tables if you already have other servers.
  3. Prefer bearer_token_env_var with VEE3_API_KEY exported - or set a literal key in http_headers.
  4. Restart Codex or start a new session, then confirm vee3 appears in codex mcp list.

config.toml

Paste into ~/.codex/config.toml, or merge the vee3 block into an existing file.

[mcp_servers.vee3]
url = "https://mcp.vee3.io/mcp"
enabled = true
bearer_token_env_var = "VEE3_API_KEY"

Verify the connection

Run codex 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