Telnyx MCP Server
Related Servers
Alternatives to Telnyx MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for TELNYX integration, enabling AI assistants to send SMS messages, make voice calls, and handle incoming communications via webhooks.MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server enabling AI assistants to make voice calls, send SMS/MMS, and manage group conversations using Twilio and OpenAI.5 npm-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects Twilio to MCP clients, enabling natural language control of SMS, MMS, WhatsApp messaging, voice calls, and phone number management.25 npmMIT
- AlicenseBqualityDmaintenanceMCP server for the seven.io API, enabling SMS, voice, RCS messaging, and account management through natural language.446 npm1MIT
- AlicenseAqualityAmaintenanceAn MCP server that lets AI assistants inspect and control Asterisk and FreeSWITCH PBX systems, enabling natural language queries about live switch status, channels, registrations, and call control.1030 npm16MIT

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.521MIT
TDQS
Scored across 46 tools
Several tools have overlapping purposes: `list_embedded_buckets` vs `cloud_storage_list_buckets`, `create_embeddings` vs `embed_url`, and `update_phone_number` vs `update_phone_number_messaging_settings` all could confuse an agent. The `update_connection` tool is a non-functional trap that always throws an exception, making it worse than useless.
Naming conventions are inconsistent across domains: some tools use `cloud_storage_*` prefix, others use plain `verb_noun`, and `mcp_telnyx_delete_assistant` is an outlier with an unusual prefix. There is no uniform pattern, though most names are readable.
With 46 tools, this server is overstuffed. It spans cloud storage, AI assistants, call control, messaging, phone numbers, and integration secrets—far too many distinct domains for a single MCP server. It would be better split into focused servers.
CRUD coverage is uneven: messaging profiles lack delete, connections lack create/delete, call control applications lack update/delete, and cloud storage lacks delete bucket. The non-functional `update_connection` tool creates a false sense of capability, and there are no update tools for integration secrets.