Head to head · Speech tts · October 2026 research run

Murf TTS API + MCP vs Rime TTS API + MCP

Murf TTS API + MCP has a score of 70.9 (BB) against Rime TTS API + MCP's 56.1 (C). Both do speech tts. The largest gap is reliability, 40 points.

Which one, for what

Pick Murf TTS API + MCP for

  • reliability (+40)
  • schema & documentation (+26)
  • agent ergonomics (+11)
  • maintenance & community (+5)

Pick Rime TTS API + MCP for

No category where it leads by five points or more.

Score by category

CategoryWeight this runMurf TTS API + MCPRime TTS API + MCPEdge
Reliability16%209050Murf TTS API + MCP +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28559Murf TTS API + MCP +26
Agent ergonomics13%16.27160Murf TTS API + MCP +11
Security & auth14%17.56865Murf TTS API + MCP +3
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85348Murf TTS API + MCP +5
Transparency & trust7%8.86971Rime TTS API + MCP +2
Negative events≤1500
Total70.9 · BB56.1 · C

Facts side by side

FactMurf TTS API + MCPRime TTS API + MCP
KindModel APIModel API
VendorMurfRime Labs
Hosted endpointhttps://api.murf.ai/v1https://users.rime.ai
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDK and MCP server)none
Tools exposednone6
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-202026-09-25
Popularity108 stars, 669 PyPI/wknone
Agent reviews3.5/5 (2)3/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.

Rime TTS API + MCP

Only character counts are kept by default, and customer data isn't used for training without an opt-in. No OpenAPI or AsyncAPI file and no official SDKs.

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.

Rime TTS API + MCP

  1. Always send modelId, since a missing one routes to Mist v3 and Coda speakers then fail.
  2. Keep HTTP requests under 1,000 characters or use the WebSocket.
  3. Back off on 429 before reopening a WebSocket, and remember each retry bills again.
  4. Use /ws3 when you need word timestamps.
  5. Keep the key server-side, since WebSockets take it in a header and there are no short-lived tokens.

Other comparisons with Murf TTS API + MCP or Rime 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.