A
licenseNot graded
qualityD
maintenanceProvides a standardized interface for interacting with Retell's tools and services through a unified API.
1
MIT
Retell AI MCP Server
Related Servers
Alternatives to Retell AI MCP Server
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage RetellAI voice services including calls, agents, phone numbers, and voices through natural language.141 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables seamless integration with ElevenLabs Conversational AI to manage agents, tools, and knowledge base sources. It supports RAG indexing, webhook integration, and document management for building advanced voice-enabled AI agents.MIT
- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.5813 npm1MIT
- FlicenseNot gradedqualityCmaintenanceAllows programmatic management of a Dify instance, including listing and creating datasets, managing applications, and tool providers.-
TDQS
A3.7/5.0
Scored across 60 tools
Disambiguation5/5
Each tool targets a distinct resource type (phone numbers, agents, calls, LLMs, knowledge bases, conversation flows, chat agents, chats, batch, concurrency, MCP tools) with clear operations. Potential overlaps like retell_create_phone_call vs retell_create_web_call are differentiated by channel, and retell_list_agents vs retell_list_chat_agents are separated by chat/voice context.
Naming Consistency5/5
All tools follow the retell_verb_noun pattern with consistent verbs (list, get, create, update, delete). Exceptions like retell_add_knowledge_base_sources and retell_publish_agent are conventional and still follow the pattern. No mixing of conventions or ambiguous verbs.
Tool Count3/5
60 tools is well above the typical 3-15 range, but the server covers a broad platform API with many resource types. Each tool maps to a distinct operation, making the count justifiable. However, the sheer number may overwhelm agents, so it is not ideal.
Completeness4/5
The tool set provides comprehensive CRUD for all major resources, including lifecycle management for agents (versions, publish) and calls (list, get, create, update, delete, register). Minor gaps exist, such as no direct update for knowledge base metadata and no delete chat session, but these are not critical dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues