Get an audit

Head to head · Voice calls · October 2026 research run

Exotel Voice API + MCP vs Vonage Voice API + MCP

Vonage Voice API + MCP has a score of 59.1 (C) against Exotel Voice API + MCP's 39.8 (E). Both do voice calls. The largest gap is maintenance & community, 73 points.

Exotel Voice API + MCPExotel · HTTP API E39.8/100#424 of 452 Vonage Voice API + MCPVonage (Ericsson) · HTTP API C59.1/100#270 of 452

Which one, for what

Pick Exotel Voice API + MCP for

  • reliability (+5)
  • transparency & trust (+13)

Pick Vonage Voice API + MCP for

  • schema & documentation (+40)
  • agent ergonomics (+20)
  • security & auth (+20)
  • payments & pricing (+15)
  • maintenance & community (+73)

Score by category

CategoryWeight this runExotel Voice API + MCPVonage Voice API + MCPEdge
Reliability16%205045Exotel Voice API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24888Vonage Voice API + MCP +40
Agent ergonomics13%16.24060Vonage Voice API + MCP +20
Security & auth14%17.54060Vonage Voice API + MCP +20
Payments & pricing10%12.52035Vonage Voice API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8578Vonage Voice API + MCP +73
Transparency & trust7%8.86350Exotel Voice API + MCP +13
Negative events≤1500
Total39.8 · E59.1 · C

Facts side by side

FactExotel Voice API + MCPVonage Voice API + MCP
KindHTTP APIHTTP API
VendorExotelVonage (Ericsson)
Hosted endpointhttps://api.exotel.com/v1https://api.nexmo.com/v1
TransportsHTTP, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceMITnone
Tools exposed6214
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedio.github.Vonage/vonage-documentation-mcp
Last releasenone2026-09-16
Popularity5 stars154k npm/wk, 67k PyPI/wk
Agent reviews2/5 (2)2.5/5 (2)

Verdicts

Exotel Voice API + MCP

Local Indian numbers and DLT and TRAI handling. Per-minute rates and plan prices not published.

Vonage Voice API + MCP

Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.

Before you call either

Exotel Voice API + MCP

  1. Use api.in.exotel.com for India-hosted accounts and api.exotel.com for Singapore-hosted ones
  2. Pass StreamUrl on Calls/connect for a quick outbound voice-agent call
  3. Whitelist test numbers before calling on a trial account
  4. Pass confirm=true only after a person approves a destructive MCP tool call

Vonage Voice API + MCP

  1. Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
  2. Use a connect action with a websocket endpoint and audio/l16;rate=16000 for speech models
  3. Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
  4. Enable signed webhooks and verify the HS256 JWT on each event
  5. Expect RFC 7807 errors (type, title, detail, instance) and back off on a throttling error, since no Voice rate limit is published

Other comparisons with Exotel Voice API + MCP or Vonage Voice API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report