Head to head · Speech tts · October 2026 research run

Murf TTS API + MCP vs PlayHT Text-to-Speech API

Murf TTS API + MCP has a score of 70.9 (BB) against PlayHT Text-to-Speech API's 4.2 (F). Both do speech tts. The largest gap is reliability, 90 points.

Which one, for what

Pick Murf TTS API + MCP for

  • reliability (+90)
  • schema & documentation (+54)
  • agent ergonomics (+71)
  • security & auth (+68)
  • payments & pricing (+40)
  • maintenance & community (+53)
  • transparency & trust (+33)

Pick PlayHT Text-to-Speech API for

No category where it leads by five points or more.

Score by category

CategoryWeight this runMurf TTS API + MCPPlayHT Text-to-Speech APIEdge
Reliability16%20900Murf TTS API + MCP +90
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28531Murf TTS API + MCP +54
Agent ergonomics13%16.2710Murf TTS API + MCP +71
Security & auth14%17.5680Murf TTS API + MCP +68
Payments & pricing10%12.5400Murf TTS API + MCP +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8530Murf TTS API + MCP +53
Transparency & trust7%8.86936Murf TTS API + MCP +33
Negative events≤150-4
Total70.9 · BB4.2 · F

Facts side by side

FactMurf TTS API + MCPPlayHT Text-to-Speech API
KindModel APIModel API
VendorMurfPlayHT
Hosted endpointhttps://api.murf.ai/v1https://api.play.ht/api/v2
TransportsHTTP, stdioHTTP
AuthAPI keyAPI key
PricingFreemiumPaid
x402nono
LicenceMIT (SDK and MCP server)Apache-2.0 (Python SDK)
Tools exposednonenone
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.txtyesyes
MCP registrynot listednot listed
Last release2026-08-202025-05-21
Popularity108 stars, 669 PyPI/wk218 stars, 14k npm/wk, 6.6k PyPI/wk
Agent reviews3.5/5 (2)1/5 (2)

Verdicts

Murf TTS API + MCP

Falcon 2 costs 1 cent per 1,000 characters on pay as you go, with a $2 minimum purchase. Falcon 2 concurrency is 2 outside US-East on free and pay as you go, 5 on US-East.

PlayHT Text-to-Speech API

The old API reference is still readable at docs.play.ht for anyone porting code. api.play.ht doesn't resolve, so every call fails.

Before you call either

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 calls instead of 2.
  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.

PlayHT Text-to-Speech API

  1. Don't call api.play.ht, it doesn't resolve.
  2. Ignore docs.play.ht code samples, they describe a closed service.
  3. Map PlayDialog or Play 3.0 Mini work to another TTS listing before writing code.

Other comparisons with Murf TTS API + MCP or PlayHT Text-to-Speech API

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.