vapi-mcp
Related Servers
Alternatives to vapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables integration with Vapi's voice AI platform to manage assistants, create and schedule phone calls with dynamic variables, and manage phone numbers through function calling.362 npmMIT
- AlicenseCqualityDmaintenanceEnables AI agents to manage Vapi Voice AI platform resources such as assistants, calls, phone numbers, analytics, and workflows through natural language.343MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage RetellAI voice services including calls, agents, phone numbers, and voices through natural language.155 npmISC
- AlicenseAqualityDmaintenanceManage voice AI agents, make calls, run campaigns, and control phone numbers through natural language.5820 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage Davoxi voice agent platform resources such as businesses, agents, call logs, webhooks, analytics, and billing through natural language conversations.17 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to control PSTN phone calls via TelePath, including dialing, hangup, and phone number management.117 npmMIT
TDQS
Scored across 8 tools
Each tool focuses on a distinct aspect of client provisioning (creation, calling, templates, prompts, phone, tools, outputs, status), but 'apply_template' and 'set_prompt_and_voice' both modify assistant settings, which could cause minor confusion. 'smoke_test_call' is clearly separate.
All names use snake_case with verb_noun pattern (provision_client, attach_phone, list_client_status), but verbs vary in style: 'provision' and 'apply' are less conventional than 'set', 'attach', 'list'. 'smoke_test_call' is a multi-word verb, a minor deviation.
8 tools is within the ideal range for a client lifecycle management server, covering provisioning, configuration, and testing. It feels slightly heavy but each tool serves a clear purpose, so it is well-scoped.
The tools cover create, read/status, update (apply_template, set_prompt_and_voice), and attach resources, but there is no explicit delete/deprovision tool, which is a notable gap for a lifecycle. The smoke_test and structured outputs are nice-to-haves, but the missing teardown functionality is a gap.