MIT
VoiceAI-MCP-VAVicky
Officialby AiAgency-Now
Related Servers
Alternatives to VoiceAI-MCP-VAVicky
No user-submitted related servers found.
Related Servers
@seldonframe/mcpofficial
AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible agents to build and operate complete AI front offices for local businesses—branded websites, booking, intake, CRM, and AI agents in one workspace.62AGPL 3.0- AlicenseCqualityDmaintenanceMulti-MCP orchestration hub connecting GHL, Stripe, Shopify, Supabase, and more through a single AI interface, enabling workflow automation and CRM management.3032 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables voice-first interactions with AI agents and MCP tools, supporting speech input/output, STT/TTS, and a provider-independent agent core.1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceUniversal AI API Orchestrator. 850 tools across 53 services under a single MCP interface. Connect Claude, GPT, or Gemini to Stripe, Slack, GitHub, LinkedIn, Cloudflare, Shopify, Twilio, and 46 more via natural language. $0.10/execution, no subscription. Patent Pending.39 npm5-
- FlicenseNot gradedqualityDmaintenanceA comprehensive sales automation platform combining Model Context Protocol (MCP) server with Gemini AI voice interface, featuring 13+ integrated sales tools and AWS deployment capabilities.-
TDQS
C2.9/5.0
Scored across 32 tools
Disambiguation3/5
Most tools have distinct purposes, but there is notable overlap between 'get_assistant' and 'get_one_assistant' which could cause confusion, as both seem to retrieve assistant information with unclear differentiation. Other tools like 'get_assistants' vs 'get_dashboard_assistant' are better distinguished by their descriptions.
Naming Consistency4/5
The naming follows a consistent verb_noun pattern throughout, such as 'create_assistant', 'update_assistant', and 'get_twilio_numbers'. Minor deviations exist, like 'chat_with_assistant' using a preposition, but overall the convention is clear and predictable.
Tool Count2/5
With 32 tools, the count is excessive for a VoiceAI server, leading to potential bloat and complexity. A more focused set of 10-20 tools would better suit the domain, as many tools (e.g., multiple token updates) could be consolidated into fewer, more general operations.
Completeness4/5
The toolset provides comprehensive coverage for VoiceAI operations, including assistant management (CRUD), Twilio integration, call handling, and token updates. Minor gaps exist, such as lacking tools for detailed call analytics or assistant testing, but core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessNo issues