KaiCalls MCP Server
OfficialRelated Servers
Alternatives to KaiCalls MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to initiate and manage real-time voice calls using Twilio and OpenAI's voice models.65MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implementation that enables AI assistants to interact with RetellAI's voice services for managing calls, agents, phone numbers, and voice options.499 npm40ISC
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with VoIPBin's VoIP services, supporting features like call management, agent management, campaigns, conferences, and chat functionality.4MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- FlicenseNot gradedqualityDmaintenanceA demonstration implementation of the Model Context Protocol server that facilitates communication between AI models and external tools while maintaining context awareness.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables LLMs and AI assistants to create, manage, and interact with isolated cloud-based Python environments with GPU support on Modal.com.111MIT
TDQS
Scored across 206 tools
Despite very long descriptions, many tools overlap in purpose: update_agent_config vs request_agent_update vs rollback_config vs request_config_rollback all change live agent settings, and buy_number vs request_number_purchase vs request_extra_number vs attach_number all target number acquisition/assignment. Similarly send_sms vs send_message, create_agent vs set_up_business, and the ~40 agency_installation/agency_enrollment/agency_billing tools create heavy boundary confusion. An agent would frequently need to read several full descriptions to pick correctly.
All snake_case, but verb placement is inconsistent: many tools are verb_noun (list_evals, create_eval, send_sms, buy_number) while large families are domain-prefixed noun_verb (agency_profile_bootstrap, agency_installation_preview_route_receipt, lsa tools get_lsa_report). Some names are nouns with no verb at all and several embed long multi-word chains, making the pattern unpredictable.
206 tools is an extreme surface for a single MCP server; the vast majority are niche agency/billing/installation admin operations that no single agent session would need. This far exceeds what a coherent toolset should expose and guarantees selection noise.
Coverage of the domain (calls, agents, numbers, SMS/WhatsApp/email, billing, agency partner flows, LSA, call tracking, evals, trust) is extensive with lifecycle tools for most resources. Minor gaps remain, e.g. no update/delete for knowledge or product rows beyond upsert, and some flows are read-only placeholders (submit_text_registration unavailable).