movoice-mcp
OfficialRelated Servers
Alternatives to movoice-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceManage voice AI agents from Claude Code, Cursor, VS Code, or any MCP-compatible assistant.37 npm3MIT
- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.5811 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access local voice synthesis, zero-shot cloning, and voice catalog tools through native MCP tool calls for applications like Claude and Cursor.17 npmAGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables Claude to launch and manage Cursor Cloud Agents on GitHub repos, including polling status, sending follow-ups, and reading conversations/PRs.18 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables voice-driven control of coding agents via Claude on your phone, allowing status checks, stand-ups, sending prompts, and receiving push notifications when agents finish or need decisions.MIT

sidevoice-connectorofficial
AlicenseNot gradedqualityAmaintenanceEnables coding agents to participate in voice calls, speaking replies while continuing their work and accepting spoken input or interruptions within the same conversation. It delivers voice input into Claude Code, Codex, Cursor, or custom HTTP endpoint workflows.Apache 2.0
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: five tools handle agent lifecycle (list/get/create/update/delete), and two handle call logs (list/get). There is no overlap or ambiguity between the tools.
All tool names follow a consistent verb_noun pattern using snake_case, such as list_agents, create_agent, delete_agent, and list_calls. This makes the API predictable and easy for an agent to navigate.
Seven tools is a well-scoped set for a voice AI agent management server. Each tool covers a meaningful operation without unnecessary redundancy or bloat.
The tool surface provides full CRUD coverage for agents and read-only access to call logs, which is exactly what the domain requires. There are no obvious missing operations that would cause agent workflows to fail.