A
licenseNot graded
qualityC
maintenanceLets any MCP-capable AI client create and manage AI voice agents without writing HTTP code.
18 npm
MIT
Dunefox Voice MCP Server
Related Servers
Alternatives to Dunefox Voice MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.5811 npm1MIT
Dial MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to provision phone numbers, send SMS, place AI voice calls, and react to inbound events via the Dial communication stack, all through MCP tools.962 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI-driven customer support operations including conversation management, knowledge base, contacts, metrics, and settings via MCP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables building, publishing, and operating CallDeskTech voice agents, including conversation flows, knowledge bases, phone routing, calls, batch calls, and webhooks.155 npmMIT
ChatRail MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables managing a ChatRail workspace from MCP clients, including checking WhatsApp connection health, looking up groups, tracing message failures, scheduling messages, and replaying webhook deliveries.MIT
TDQS
B3.2/5.0
Scored across 25 tools
Disambiguation4/5
Most tools have clearly distinct resource/action purposes, and descriptions actively disambiguate easily confused pairs like get_campaign vs. get_campaign_report, get_call vs. get_transcript, and place_call vs. send_announcement. Some boundaries remain slightly soft, particularly around call detail vs. transcript retrieval and agent listing vs. agent detail, but an agent can generally select correctly.
Naming Consistency5/5
The tool set uses a highly consistent snake_case verb_noun convention (list_calls, get_call, create_campaign, update_agent, delete_webhook, etc.). The few special cases such as whoami and get_lead_for_call are conventional and still readable, without mixing camelCase or conflicting verb styles.
Tool Count3/5
At 25 tools, the server is on the heavy side for the apparent scope, covering campaigns, calls, agents, leads, webhooks, and announcements. The domain is broad enough that many tools earn their place, but the surface is close to the rubric's borderline-heavy range and could benefit from consolidation.
Completeness3/5
Core lifecycles for campaigns and agents are well covered, including create, read, list, update, delete, and reporting. However, there are notable gaps such as lead update/delete, announcement listing or cancellation, and webhook update/detail operations, which may force workarounds for full lifecycle management.
Maintenance
ActivityMaintained
ResponsivenessNo issues