Connect Vee3 MCP to Hermes Agent
Published: July 8, 2026
Ask your agent
RecommendedCopy and paste this into Hermes chat and let the agent walk you through setup.
Agent Instruction
Connect to Hermes Agent
Add Vee3 as a remote HTTP MCP server in config.yaml.
- Open or create
~/.hermes/config.yaml. - Paste the config from the copy block below under
mcp_servers.- New file: paste the whole block (starts with
mcp_servers:). - Already has servers: add only the
vee3entry - do not duplicatemcp_servers.
- New file: paste the whole block (starts with
- Set your API key in
headers, or addVEE3_API_KEY=vee3_live_...to~/.hermes/.envand keep${VEE3_API_KEY}in the YAML. - Save the file, then run
/reload-mcpin Hermes chat. - Test - e.g. “Capture a screenshot of https://example.com”. Tools appear as
mcp_vee3_…(Hermes prefixes server names).
config.yaml (HTTP - recommended)
RecommendedUses ${VEE3_API_KEY} - set that variable in your shell or ~/.hermes/.env.
mcp_servers:
vee3:
url: https://mcp.vee3.io/mcp
headers:
VEE3_API_KEY: ${VEE3_API_KEY}
Alternative: stdio via mcp-remoteShowHide
Use this only if direct HTTP does not work in your environment. Requires Node.js and npx.
config.yaml (stdio bridge)
Replace the vee3 HTTP block with this stdio entry, or use it instead 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}"
Hermes tool names are prefixed
The screenshot tool registers as something like mcp_vee3_website_screenshots_capture. Mention vee3 or that tool name in your prompt.
Hermes uses ${VAR} env substitution. Do not commit literal API keys.
Verify the connection
Run /reload-mcp after saving config changes, then ask the agent to call meta-tools.list_groups or search the catalog with meta-tools.search. Hermes registers tools with the mcp_vee3_ prefix (for example mcp_vee3_meta_tools_list_groups). 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.