Vox MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | No | API key for xAI | |
| DEFAULT_MODEL | No | Default model, default 'auto' | |
| CUSTOM_API_URL | No | Custom API URL for Ollama, vLLM, etc. | |
| GEMINI_API_KEY | No | API key for Google Gemini | |
| OPENAI_API_KEY | No | API key for OpenAI | |
| DEEPSEEK_API_KEY | No | API key for DeepSeek | |
| MOONSHOT_API_KEY | No | API key for Moonshot (Kimi) | |
| ANTHROPIC_API_KEY | No | API key for Anthropic | |
| OPENROUTER_API_KEY | No | API key for OpenRouter | |
| MAX_CONVERSATION_TURNS | No | Thread length limit, default 100 | |
| VOX_FORCE_ENV_OVERRIDE | No | Force .env override of client env vars | |
| CONVERSATION_TIMEOUT_HOURS | No | Thread TTL in hours, default 24 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chatA | Multi-model AI gateway. Routes prompts to external AI models (Gemini, OpenAI, Anthropic, DeepSeek, Moonshot, xAI, OpenRouter, custom endpoints) with conversation memory. Supports file context embedding, images, and multi-turn threads via continuation_id. |
| listmodelsA | Shows which AI model providers are configured, available model names, their aliases and capabilities. |
| dump_threadsA | Export conversation threads as JSON or Markdown. Threads persist to disk and can be cold-reloaded after memory expiry. Use thread_ids to filter specific threads, format to choose output. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
chat, dump_threads, and listmodels have clearly distinct purposes: sending prompts, exporting conversation threads, and listing available models. There is no overlap or ambiguity in which tool to use for each task.
The set mixes naming conventions: 'chat' is a single lowercase word, 'dump_threads' uses snake_case verb_noun, and 'listmodels' is a concatenated lowercase noun phrase. While still readable, the pattern is inconsistent.
Three tools is lean but reasonable for a focused multi-model gateway covering chat, export, and model discovery. It could benefit from one or two additional thread-management tools, but nothing feels excessive.
Core operations are present: chatting, exporting threads, and listing models. However, obvious lifecycle operations like deleting or clearing threads are missing, and there is no way to list threads independently of exporting them.