pbx-mcp
Related Servers
Alternatives to pbx-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceThis MCP server enables AI assistants to read PBX state—extensions, DID numbers, SIP trunk providers, tenants, and live statistics—from ICTPBX via the ICTCore REST API, without placing calls or changing configuration.5222 npm16MIT- AlicenseNot gradedqualityBmaintenanceAn MCP server enabling AI assistants to make voice calls, send SMS/MMS, and manage group conversations using Twilio and OpenAI.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI assistants to manage Cisco Unified Communications Manager (CUCM) via AXL SOAP API, supporting provisioning, configuration, and database queries through natural language.36 npm7MIT
- FlicenseCqualityDmaintenanceMCP server enabling interaction with Telnyx telephony, messaging, and AI assistant APIs through natural language.46-

VoIPbin MCP Serverofficial
AlicenseBqualityCmaintenanceAn MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.6625 PyPI1MIT- AlicenseNot gradedqualityBmaintenanceMCP server that connects AI assistants to Five9 contact center, allowing management of campaigns, agents, lists, and statistics via natural language commands.17MIT
TDQS
Scored across 12 tools
Tools are cleanly partitioned by platform prefix (asterisk_* vs freeswitch_*) and each resource is distinct: channels vs endpoints vs status vs sofia profiles answer different questions. The main overlap is that asterisk_cli/freeswitch_api can reproduce nearly everything the specialized tools do, but the descriptions steer agents toward the purpose-built tools and the read-only default limits the damage.
Consistent snake_case with a predictable platform_resource pattern (asterisk_channels, freeswitch_registrations, etc.), mirrored neatly across both subsystems. The only blemish is that the raw-command tool is called asterisk_cli on one side and freeswitch_api on the other, so the parallel naming breaks for that one pair.
12 tools split roughly six-and-six across two PBX platforms, with each tool earning its place (status, channels, registrations, dialplan/profiles, raw command, hangup preview). Well within a comfortable range for the scope.
Both *_hangup_preview tools explicitly reference an asterisk_hangup / freeswitch_hangup counterpart that does not exist in the surface, leaving the previews as dead ends an agent cannot act on. Read-only inspection is otherwise well covered, but there is no originate, no queue/voicemail-specific tools, and no write path beyond flipping the raw CLI/API escape hatch.