Vox MCP
Related Servers
Alternatives to Vox MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceEnables AI assistants to intelligently select and switch between different AI models (OpenAI, Anthropic, etc.) within the same conversation based on task requirements. Provides a unified interface for accessing multiple AI providers through a single MCP tool.121 npmMIT
- FlicenseNot gradedqualityCmaintenanceMulti-cloud MCP server that exposes cloud AI models as tools for AI CLI agents, supporting streaming, conversation history, parallel multi-model queries, and dynamic model discovery.2-
- AlicenseNot gradedqualityDmaintenanceMCP of MCPs. Automatic discovery and configure MCP servers on your local machine. Integration with Claude and Cursor.53Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables real-time communication and shared vector memory between Claude Code, OpenAI Codex CLI, and Google Gemini CLI. It allows different AI platforms to exchange messages, share context, and collaborate through a unified MCP interface.MIT
- AlicenseNot gradedqualityDmaintenanceMulti-model AI conversation MCP for Claude Desktop. Seamlessly integrate with GPT-4, Gemini, xAI, Perplexity, and local models via Ollama.MIT
- AlicenseAqualityCmaintenanceProvides a unified MCP interface to interact with Codex CLI, Claude Code, and Grok API, allowing seamless switching between AI models in VS Code or Claude Code.2MIT
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.