Dunefox Voice MCP Server
Related Servers
Alternatives to Dunefox Voice MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP clients to manage AI voice assistants, place calls, run campaigns, handle contacts and knowledge bases, and read call transcripts. It also provides account, phone number, dialer, and analytics tools through a hosted or local MCP connection.25MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to place and manage outbound phone calls, handle inbound calls with a realtime voice agent, add live context, send DTMF digits, and retrieve structured call outcomes and transcripts.MIT
- AlicenseNot gradedqualityBmaintenanceLets any MCP-capable AI client create and manage AI voice agents without writing HTTP code.278 npmMIT
- 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.775 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI-driven customer support operations including conversation management, knowledge base, contacts, metrics, and settings via MCP.MIT
TDQS
Scored across 25 tools
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.
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.
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.
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.