crazytel
Related Servers
Alternatives to crazytel
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 gradedqualityDmaintenanceProvides comprehensive access to Telnyx's telephony and communication services including call control, SMS/MMS messaging, fax, number management, and SIM card operations. Implements 822 API endpoints from Telnyx API v2.0.0 for complete telecommunications functionality.MIT
- AlicenseCqualityBmaintenanceEnables interaction with Mango Office cloud PBX to manage calls, users, recordings, SMS, and call statistics.833 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Rostelecom Virtual PBX telephony, including contacts, subscribers, call groups, call history, call recordings, numbers and routing, balance, and transparent proxy to any of ~240 endpoints.MIT

clicksend-mcp-serverofficial
AlicenseBqualityCmaintenanceEnables AI assistants to send SMS and manage messaging workflows through ClickSend, including pricing estimates, contact lists, templates, history, and statistics.671 npm3MIT- AlicenseBqualityDmaintenanceEnables interaction with the Telnyx API for billing, phone numbers, and messaging.1217 PyPIMIT
TDQS
Scored across 42 tools
Core CRUD areas are separated by resource (contacts, contact lists, DIDs, SIP trunks, opt-outs, SMS), and descriptions clarify boundaries. However, list_dids / list_sms_dids and list_messages / list_conversations / get_conversation overlap enough that an agent could initially confuse them.
The majority follow a clean list/get/create/update/delete_<resource> pattern with consistent resource nouns. Minor exceptions like add_contacts_to_list, check_opt_out, and bulk_send_sms break the pattern but remain readable.
42 tools is well beyond the range where an agent can easily keep the full surface in context, and many are close list/get variants (e.g., three SMS stats tools, two DID list tools). It would be more coherent split into SMS/DID/contacts sub-servers.
The core CRUD for contacts, contact lists, DIDs, and SIP trunks is covered, plus SMS send/bulk/schedule and stats. But opt-out lists/entries have create/list/check without delete/update, scheduled messages cannot be canceled, and contact lists have add but no remove member operation.