Head to head · Text-to-speech · October 2026 research run

ElevenLabs Text to Speech API + MCP vs Murf TTS API + MCP

ElevenLabs Text to Speech API + MCP scores 77.8 (BB) on agent readiness against Murf TTS API + MCP's 72 (BB), and leads in 4 of 7 scored categories. Murf TTS API + MCP leads on reliability. Both do text-to-speech.

Best text-to-speech APIs for AI agents · All 148 tts comparisons

Which one, for what

ElevenLabs Text to Speech API + MCP BB

Best for Best when an agent needs many languages, many voices or the most expressive models from one vendor, and the operator can accept training by default or pay for Enterprise.

Ahead on

  • Schema & documentation, 94 against 85
  • Agent ergonomics, 92 against 71

Also in its favour

  • No incidents deducted, where Murf TTS API + MCP loses 3 points for them

Watch for

Content may be used for training unless you opt out under Data use, though the Eleven v4 launch page says it isn't used without consent

Murf TTS API + MCP BB

Best for Budget voice-agent output where 2 to 5 concurrent streams are enough, or for studio-style renders on Gen2.

Ahead on

  • Reliability, 90 against 80

Watch for

Falcon 2.1 concurrency is 2 outside US-East on free and pay as you go, 5 on US-East

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics ElevenLabs Text to Speech API + MCP +21

ElevenLabs Text to Speech API + MCP 92

API reading of the checklist. MP3, PCM, WAV, Opus, mu-law and A-law output, streaming over HTTP or WebSocket, and character timestamps on a separate endpoint so you only pay the payload when you ask for it. Higher-quality formats are gated by plan (22 of 25). Per-request character caps published per model (40,000 on Flash v2.5, 10,000 on v4 and Multilingual v2, 5,000 on v3). GET /v2/voices pages with page_size (default 10) and next_page_token and filters by search, category, language, gender, age, accent and use case, and /v1/shared-voices pages the Voice Library with a sort enum (20). Errors carry type, code, message, param and request_id (20). Backoff guidance for 429, and an optional seed for best-effort repeatable output. Nothing found on whether failed calls are billed. Since 26 October requests priced below one credit are charged one credit, and refunds return the credits charged (15 of 20). Only the text and a voice ID are required, model_id defaults to Multilingual v2 on Text to Speech and to v3 on Text to Dialogue, output_format to 128 kbps MP3, and official SDKs ship in Python and TypeScript (15).

Murf TTS API + MCP 71

Read as an API. Output in MP3, WAV, FLAC, A-law, mu-law or Base64 at 8 to 48 kHz, with word timestamps, streaming over HTTP or WebSocket, and inline Base64 instead of a download link (22 of 25). Per-request cap of 3,000 characters documented and the voice list filters by model, but there's no length control beyond splitting text yourself (12 of 20). Machine-readable error and warning codes with a trace_id (18 of 20). Backoff guidance documented (10). Nothing found on whether failed calls are billed and no seed for repeatable output (0 of 10). Three required fields including locale, and the only official SDK is Python (9 of 15).

Reliability Murf TTS API + MCP +10

ElevenLabs Text to Speech API + MCP 80

incident.io status page with a Text-to-Speech component and dated history (20). Re-read on 1 November from the history page (the incidents feed was re-posted on 21 October and now lists 25 incidents, none of them TTS). Four incidents touched the Text to Speech component in the 90 days from 3 August, all at degraded performance. Elevated TTS and STT error rates from 06:39 to 07:13 UTC on 3 August, posted after it was fixed, elevated TTS and STT latency from 15:15 to 17:53 UTC on 26 August (2 hours 38 minutes, not the 6 hours the 17 October note gave), about 3 hours of increased latency on 6 October (09:09 to 12:14 UTC) and 11 minutes of TTS failures and latency during a traffic spike on 12 October. The partial outages in that time hit Agents components, Telephony, Dubbing and STT, among them about 5 hours of US timeouts on 13 October whose affected components don't include Text to Speech. Nothing has touched TTS since 12 October (20). TTS concurrency per plan published with numbers, re-read on 1 November, 2 on Multilingual v2 and 4 on Flash for Free up to 15 and 30 on Scale, with current-concurrent-requests and maximum-concurrent-requests response headers (15). The error reference returns rate_limit_exceeded and concurrent_limit_exceeded as 429 and asks for exponential backoff (15). No SLA found for self-serve plans, and the API pricing page still puts SLAs under Enterprise (0). The TTS endpoints and Eleven v4 carry no alpha or beta label (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.

Murf TTS API + MCP 90

Atlassian status page at murf.statuspage.io, linked from the rate-limits doc, with history back to February 2024 (20). No incident posted since 2025-09-22, still so on 1 November 2026, so the 90-day record is clean. The page tracks only two components (API and Studio), so a clean record says less than a page with a component per region (30). Concurrency limits published per model and region, 5 on US-East and 2 elsewhere for Falcon 2.1 on free and pay as you go, and since 22 October Falcon 2.1 streaming responses report the region, limit and slots in use (15). The errors page tells you to retry 429, 500 and 503 with exponential backoff (15). No SLA found on any self-serve tier (0). Falcon 2.1 carries no beta label (10).

Schema & documentation ElevenLabs Text to Speech API + MCP +9

ElevenLabs Text to Speech API + MCP 94

OpenAPI file at api.elevenlabs.io/openapi.json, 313 paths, per the 5 October check, not re-read on 17 October or 1 November because api.elevenlabs.io's robots.txt disallows it (25). llms.txt with a Markdown twin of every page, re-read on 1 November (10). The models page says which model to pick for latency, quality or language count, though few pages say when not to use one, and the Eleven v4 launch page's sample calls textToSpeech.convert while the docs route v4 through Text to Dialogue (16 of 20). Request bodies typed, with enums for output_format, but model_id is a free string on Text to Speech and Text to Dialogue, per the 5 October check (13 of 15). Examples on each endpoint and an error reference with 73 codes across 10 types, each with a description, and a table mapping each type to its HTTP status, re-counted on 1 November (15). Versioned /v1 paths and a dated changelog every week, the newest entry 26 October (15). 25 + 10 + 16 + 13 + 15 + 15 = 94.

Murf TTS API + MCP 85

OpenAPI and AsyncAPI specs listed in llms.txt (25). llms.txt with Markdown twins of every page (10). Model pages say which model suits voice agents and which suits studio renders, and the changelog flags Gen2 streaming as deprecated (15 of 20). Typed request bodies in the spec, with text, voiceId and locale required. We didn't check every enum (10 of 15). The errors page lists 7 HTTP codes, 4 WebSocket errors and 8 warnings, each with cause and fix, but covers only the streaming and WebSocket APIs (13 of 15). Dated public changelog, a single /v1 path and one breaking rename in 2026 (multiNativeLocale to locale on 2026-03-05) (12 of 15).

Score by category

CategoryWeightElevenLabs Text to Speech API + MCPMurf TTS API + MCPEdge
Reliability16%8090Murf TTS API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9485ElevenLabs Text to Speech API + MCP +9
Agent ergonomics13%9271ElevenLabs Text to Speech API + MCP +21
Security & auth14%6568Murf TTS API + MCP +3
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7773ElevenLabs Text to Speech API + MCP +4
Transparency & trust7%6867ElevenLabs Text to Speech API + MCP +1
Negative events≤150-3
TotalBB 77.8/100BB 72/100

Facts side by side

FactElevenLabs Text to Speech API + MCPMurf TTS API + MCP
KindModel APIModel API
VendorElevenLabsMurf
Hosted endpointhttps://api.elevenlabs.io/v1https://api.murf.ai/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs)MIT (SDK and MCP server)
Read-only variant documentednono
llms.txtyesyes
MCP registryio.elevenlabs/mcpnot listed
Last release2026-10-272026-08-20
Terms last updated2026-03-31no date given
Privacy policy last updated2026-05-20no date given
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity3.1k stars, 1.1M npm/wk, 2.2M PyPI/wk108 stars, 669 PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

What the same task costs

TaskElevenLabs Text to Speech API + MCPMurf TTS API + MCP
Narrate a 9,000-character scriptabout 1,500 words$0.36 to $0.72$0.09 to $0.27

Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.

How the scores have moved

Verdicts

ElevenLabs Text to Speech API + MCP

Keys can be limited to chosen endpoints and given a credit quota, and service accounts hold keys that don't belong to a person. The Terms let ElevenLabs train on content unless you opt out, which the Eleven v4 launch page contradicts, and v4 runs through Text to Dialogue rather than the classic text-to-speech endpoint.

Murf TTS API + MCP

Falcon 2.1 costs 1 cent per 1,000 characters on pay as you go, with a $2 minimum purchase. Concurrency is 2 outside US-East on free and pay as you go, 5 on US-East, and on 19 October 2026 the falcon-2 identifier switched to Falcon 2.1 on the day it was announced.

Before you call either

ElevenLabs Text to Speech API + MCP

  1. Call Eleven v4 through POST /v1/text-to-dialogue and set model_id to eleven_v4, because that endpoint defaults to eleven_v3.
  2. Retrain an older Instant or Professional Voice Clone on v4 before using it there, since earlier clones aren't tuned for the new model.
  3. Spell out numbers yourself on eleven_flash_v2_5, which doesn't normalise them by default, and turning that on is Enterprise only.
  4. On 429 read code, back off on rate_limit_exceeded and wait for running requests on concurrent_limit_exceeded.
  5. Give the agent a key scoped to Text to Speech with a credit quota and, for a fixed server, an IP allowlist.

Murf TTS API + MCP

  1. Send locale on every request, since multiNativeLocale was replaced on 2026-03-05.
  2. Split text into chunks under 3,000 characters per request.
  3. Use the US-East host for 5 concurrent Falcon 2.1 calls instead of 2, and read X-Murf-Concurrency-Remaining before opening more
  4. Set encodedAsBase64 to get audio inline and skip the expiring download link.
  5. Back off on 429 and close WebSocket contexts with end: true to free slots.
  6. Send model: "falcon-2.1" and list voices with the same model, since each model has its own voice catalogue

Questions

Which is better for AI agents, ElevenLabs Text to Speech API + MCP or Murf TTS API + MCP?

ElevenLabs Text to Speech API + MCP scores 77.8 (BB) on agent readiness against Murf TTS API + MCP's 72 (BB), and leads in 4 of 7 scored categories. Murf TTS API + MCP leads on reliability.

Do ElevenLabs Text to Speech API + MCP and Murf TTS API + MCP need an API key?

ElevenLabs Text to Speech API + MCP takes an API key or an OAuth sign-in. Murf TTS API + MCP needs an API key.

Can an agent call ElevenLabs Text to Speech API + MCP and Murf TTS API + MCP without installing anything?

Yes. ElevenLabs Text to Speech API + MCP has a hosted endpoint at https://api.elevenlabs.io/v1 and Murf TTS API + MCP at https://api.murf.ai/v1.

Other comparisons with ElevenLabs Text to Speech API + MCP or Murf TTS 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.