mcp-server
Provides a Model Context Protocol (MCP) server for integrating Vapi voice assistants/phone agents with MCP-capable AI clients. Exposes tools to manage Vapi assistants, create/schedule outbound calls, manage phone numbers, and manage custom tools, including an OAuth-based login/logout flow and support for connecting to a hosted remote MCP endpoint.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses HTTPS remote endpoint and Authorization: Bearer header for remote MCP; local configuration uses VAPI_TOKEN env var. However, README does not document rate limits, scopes, or detailed security/error handling behavior, and dependency health/security posture is not evidenced beyond package manifest.
⚡ Reliability
Best When
You want an MCP tool interface to Vapi for assistant creation and call/number management from an MCP-capable AI client (e.g., Claude Desktop/Code).
Avoid When
You need guaranteed retry/idempotency semantics or detailed operational guarantees (pagination, error codes, rate-limit values, SLA) that are not documented here.
Use Cases
- • Building AI voice assistants that can schedule and manage appointments via phone calls
- • Creating outbound call campaigns from an MCP-connected assistant
- • Managing Vapi phone numbers through an AI tool-calling workflow
- • Creating and maintaining Vapi custom tools for deeper integrations
- • Interactive agent-assisted development of voice agents using Claude/other MCP clients
Not For
- • Use as a general-purpose telephony API without Vapi context
- • Workloads needing strong enterprise compliance documentation (not evidenced in provided README)
- • Use cases requiring clearly documented idempotency guarantees (not evidenced in provided README)
Interface
Authentication
README describes OAuth-based login (via MCP tools) and bearer token usage for remote MCP, but does not describe fine-grained scopes.
Pricing
No pricing or free-tier details are present in the provided README/content.
Agent Metadata
Known Gotchas
- ⚠ Potential non-idempotency of operations like create/update/delete calls; README does not state idempotency or safe retry behavior.
- ⚠ First-time OAuth/browser sign-in may be required depending on client configuration (Claude Code).
- ⚠ Remote MCP endpoint differs from deprecated SSE; ensure clients use the recommended streamable HTTP endpoint.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.