standard-vocal-mcp
Related Servers
Alternatives to standard-vocal-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables autonomous prompt improvement for voice AI agents through feedback analysis, test generation, and iterative testing.10-
- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.5813 npm1MIT

movoice-mcpofficial
AlicenseAqualityCmaintenanceCreate and manage voice AI agents using natural language from Claude Desktop or Cursor. Enables agent creation, listing, updating, deletion, and viewing call logs.73 npmMIT
Pinecall MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables coding agents to build, test, and deploy production voice agents with real phone numbers directly from the editor, including live call monitoring and sandboxed development.23 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to enroll and verify voice samples against known identities, providing honest confidence signals about voice authenticity.1MIT
- AlicenseAqualityAmaintenancePolicy-based governance for AI agent tool calls. YAML policies, approval gates, risk assessment, and audit logging across LangChain, OpenAI, Anthropic, and MCP.551 PyPI15MIT
TDQS
Scored across 6 tools
Each tool targets a distinct responsibility: listing, deploying, evaluating, analyzing audio, diffing prompts, and gating regressions. Even run_eval and regression_gate are clearly separated, with the former generating scores and the latter comparing against a baseline.
The first three tools follow a verb_noun pattern (list_agents, deploy_agent, run_eval), while the last three are noun-centric (audio_forensics, prompt_diff, regression_gate). This split in grammatical structure makes the naming convention inconsistent and harder to predict.
Six tools is well-scoped for a specialized server focused on voice agent lifecycle and evaluation. Every tool earns its place, and the count is neither too small nor bloated.
The set covers the core workflow: discover agents, deploy new ones, run tests, analyze call audio, version prompts, and gate updates. Minor gaps include no delete_agent or direct update_agent, but these are not critical for the server's apparent purpose.