Vox MCP

What this does

Vox MCP exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GEMINI_API_KEY
OPENAI_API_KEY
ANTHROPIC_API_KEY
XAI_API_KEY
DEEPSEEK_API_KEY
MOONSHOT_API_KEY
OPENROUTER_API_KEY
CUSTOM_API_URL
CLOUDFLARE_API_TOKEN
CLOUDFLARE_ACCOUNT_ID
CLOUDFLARE_GATEWAY_ID
CLOUDFLARE_MODELS
VERCEL_AI_GATEWAY_API_KEY
AI_GATEWAY_API_KEY
VERCEL_MODELS
CLOUDFLARE_ALLOWED_MODELS
VERCEL_ALLOWED_MODELS
DEFAULT_MODEL
VOX_CONFIG_PATH

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Vox MCP?

Run the Claude Code command in the install section to add Vox MCP to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Vox MCP?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Vox MCP as well.

Does Vox MCP need an API key?

Yes. Before it can run, set these environment variables: GEMINI_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, XAI_API_KEY, DEEPSEEK_API_KEY, MOONSHOT_API_KEY, OPENROUTER_API_KEY, CUSTOM_API_URL, CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, CLOUDFLARE_GATEWAY_ID, CLOUDFLARE_MODELS, VERCEL_AI_GATEWAY_API_KEY, AI_GATEWAY_API_KEY, VERCEL_MODELS, CLOUDFLARE_ALLOWED_MODELS, VERCEL_ALLOWED_MODELS, DEFAULT_MODEL, VOX_CONFIG_PATH. They go in the env block of your MCP config.