A
licenseNot graded
qualityC
maintenanceEnables AI agents to manage phone numbers, send/receive SMS, and place voice calls through natural language, connecting to the phone network via the AgentPhone API.
281 npm
124
MIT
wixzel-phone-mcp
by aqeelshamz
Related Servers
Alternatives to wixzel-phone-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search the marketplace, compare routes, send SMS, place and track calls, run phone verifications, and check account balance.MIT
- AlicenseNot gradedqualityDmaintenanceEnables integration with Vapi's voice AI platform to manage assistants, create and schedule phone calls with dynamic variables, and manage phone numbers through function calling.564 npmMIT
@telitask/mcp-serverofficial
FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage phone calls, contacts, and tasks directly, including making and scheduling calls, retrieving transcripts, and handling contact and to-do items.1-- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.589 npm1MIT
- FlicenseBqualityDmaintenanceEnables interaction with Retell AI's voice and chat agent platform. Build, deploy, and manage AI phone agents, configure conversation flows, handle calls/chats, and manage phone numbers through natural language.52-
TDQS
A3.7/5.0
Scored across 56 tools
Disambiguation4/5
Tools are organized into clear resource families (agents, calls, leads, campaigns, trunks, numbers, billing) and the verb+resource naming makes most selections obvious. The only mild ambiguities are the SIP diagnostics (check_sip_trunk_status vs test_sip_trunk) and the several billing/usage views, but their descriptions explicitly differentiate them.
Naming Consistency5/5
All tools follow a consistent lowercase snake_case verb_noun convention: list_/get_ for reads and create_/update_/delete_ for writes, plus domain verbs like start_, pause_, place_, hangup_, check_, and rotate_. Minor variants like import_leads or create_topup still fit the same predictable pattern.
Tool Count1/5
At 56 tools, this is beyond the rubric's 50+ extreme-mismatch threshold and far too large a surface for an agent to navigate efficiently. Although the tools are well structured, this is more like a full REST API than a scoped MCP server.
Completeness4/5
Most resources have full CRUD coverage plus domain-specific operations: calls, SIP diagnostics, billing views, API key lifecycle, and bulk lead import. The main gap is the campaign lifecycle: there is no update_campaign, stop_campaign, or explicit resume_campaign, so agents must delete/recreate or improvise with pause/start.
Maintenance
ActivityMaintained
ResponsivenessNo issues