# Google Cloud Text-to-Speech vs Murf TTS API + MCP

> Murf TTS scores 69.5 (B) to Google Cloud Text-to-Speech's 66.9 (B) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/google-cloud-tts-vs-murf-tts
- Markdown: https://www.anchorterminal.com/compare/google-cloud-tts-vs-murf-tts.md (~5,000 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Murf TTS API + MCP scores 69.5 (B) on agent readiness against Google Cloud Text-to-Speech's 66.9 (B), and leads in 5 of 7 scored categories. Google Cloud Text-to-Speech leads on security & auth and transparency & trust. Both do text-to-speech.

- Google Cloud Text-to-Speech: grade B, 66.9/100, rank #350 of 1486. Markdown https://www.anchorterminal.com/tools/google-cloud-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/google-cloud-tts.json
- Murf TTS API + MCP: grade B, 69.5/100, rank #239 of 1486. Markdown https://www.anchorterminal.com/tools/murf-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/murf-tts.json
- Best text-to-speech APIs for AI agents: https://www.anchorterminal.com/best/text-to-speech/index.md
- All 148 tts comparisons: https://www.anchorterminal.com/compare/text-to-speech/index.md

## Which one, for what

### Google Cloud Text-to-Speech (B)

Good for: Teams already on Google Cloud wanting many languages, SSML and an SLA.

Ahead on:
- Security & auth, 80 against 68
- Transparency & trust, 87 against 67

Also in its favour:
- No incidents deducted, where Murf TTS API + MCP loses 3 points for them

Watch for: No release note since 30 December 2025, though a Gemini 3.1 TTS preview model is listed

### Murf TTS API + MCP (B)

Good 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 85
- Schema & documentation, 85 against 80
- Agent ergonomics, 71 against 65
- Payments & pricing, 40 against 20
- Maintenance & community, 73 against 25

Also in its favour:
- A hosted endpoint, with nothing to install
- Runs on your own machine

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

### Maintenance & community: Murf TTS API + MCP +48

- Google Cloud Text-to-Speech (25): Read as a model. The newest release note is still 30 December 2025 (Chirp 3 HD in yue-HK), 311 days ago, and `gemini-3.1-flash-tts-preview` appears on the Gemini-TTS page with no dated note (0). In the 90 days from 8 August the Python client shipped 2.38.0 on 1 October, whose only change declares Python 3.15 support, which counts half and can't set the recency line (0). Release notes, a public issue tracker and paid support (10 of 15). Official client libraries, Python at 2.38.0 and Node at 7.2.0 (10 of 15). Package CI not checked (5 of 10). Total 25.
- Murf TTS API + MCP (73): Read as a model. Newest changelog entry 2026-10-27 (List Voices takes a model), after Falcon 2.1 on 2026-10-19 (30). Seven dated changelog entries in the 90 days from 3 August, on 5, 9, 13, 15, 19, 22 and 27 October, plus `murf-mcp` 0.1.14 on 2026-08-20 (10). Gen2 streaming was switched off on 2026-10-05 after a 20 July notice that named only the 16 August deprecation date, and on 19 October `falcon-2` began serving Falcon 2.1, announced the same day (0 of 10). Public changelog and a help centre (10 of 15). The Python SDK had no open issues on 1 October, per that check, not re-read on 1 November (8 of 10). Official SDK in Python only, 2.3.0 still the newest tag on 1 November, from 2026-03-05 (8 of 15). Fern-generated with a CI workflow, Python 3.8 and later (7 of 10). 30+10+0+10+8+8+7 = 73.

### Payments & pricing: Murf TTS API + MCP +20

- Google Cloud Text-to-Speech (20): No x402, MPP or L402 (0). Per-character and per-token prices for every voice family published without a login (20). Monthly free characters (1 million for Chirp 3 HD, 4 million for Standard and WaveNet) need billing enabled, which needs a card (0). A person creates a project and billing account in a browser (0). Total 20.
- Murf TTS API + MCP (40): No x402, MPP or L402 (0). Falcon 2 at 1 cent per 1,000 characters and Gen2 at $0.03, published in the docs without a login (20). 100,000 free characters with no time limit behind a Get Free API Key button. We found no card step in the docs or FAQ (20). A person signs up in a browser to get the key (0).

### Transparency & trust: Google Cloud Text-to-Speech +20

- Google Cloud Text-to-Speech (87): Closed service under the Google Cloud terms, with Apache-2.0 clients (15). The data logging page, the terms and the privacy notice agree that TTS text and audio aren't logged, and a DPA and sub-processor list exist, as read for google-speech-to-text (25 of 30). Release notes mark preview and GA, and the Cloud terms carry notice before a GA capability is discontinued, but Gemini-TTS is moving to the Agent Platform API with no dated notice for the Cloud TTS models (15 of 20). Regional endpoints (global, us, eu and others) and a public sub-processor list (20). Total 75.
- Murf TTS API + MCP (67): Closed service under clear terms, SDK and MCP server MIT (15). Data statements still disagree on 1 November. The security page says all customer data is housed in AWS us-east-2 with all storage in that region, while Falcon 2.1 runs on 11 regional hosts and a global router, and the subprocessor list names Azure, Google Cloud, IBM Cloud and Lambda Labs for speech synthesis. Download links last 72 hours by the TTS overview and 24 hours by the Enterprise page (12 of 30). Deprecations dated in the changelog, with no written policy and short or same-day notice (10 of 20). Subprocessor list with locations, last updated 30 January 2025, re-read on 1 November (15 of 20).

### Security & auth: Google Cloud Text-to-Speech +12

- Google Cloud Text-to-Speech (80): Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. OAuth 2.0 with service accounts and IAM roles per project (30). The discovery document lists `access_token`, `oauth_token` and `key` as query parameters, so 10 off, as every Google API listing in this run (20 of 30). The data logging page says Google doesn't log any customer Cloud TTS text or audio (20). The service is stateless and keeps no content (15). Because it is stateless, Data Access audit logs don't apply, leaving admin activity only (5 of 15). Valid security.txt, Google's vulnerability reward programme, SOC 2 and ISO 27001 and public Cloud security bulletins, as on google-speech-to-text (20). Total 80.
- Murf TTS API + MCP (68): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One `api-key` header, plus a generate-token endpoint for short-lived client tokens. No key scopes found (23 of 30). The docs say customer text and audio never feed Murf's model training (20). Download links last 72 hours by the TTS overview and 24 hours by the Enterprise FAQ, and `encodedAsBase64` returns audio with nothing stored, so zero retention is self-serve but not the default (10 of 15). The dashboard shows daily and monthly usage, not per-call logs (5 of 15). SOC 2 Type II, ISO 27001 and ISO 42001 on the security page. No security.txt, disclosure policy or bug bounty found (10 of 20).

### Agent ergonomics: Murf TTS API + MCP +6

- Google Cloud Text-to-Speech (65): API reading of the checklist. Audio returns Base64 in JSON or streams over gRPC, with encoding, sample rate and timepoints selectable (15 of 25). `voices.list` filters by language code with no paging, and operations list with page tokens (15 of 20). Standard gRPC status codes with messages, generic rather than TTS-specific (15 of 20). Synthesis is stateless and long audio runs as an operation, with no idempotency key (10 of 20). A first call needs a project, billing, OAuth credentials and a voice, and Cloud Storage for long audio. Official client libraries in many languages, of which Python and Node were checked (10 of 15). Total 65.
- 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 +5

- Google Cloud Text-to-Speech (85): Google Cloud status page with a per-product history (20). None of the four Google Cloud incidents since 8 August (20 August, 1 September, 8 and 9 October, and the europe-west2 incident of 20 October, which listed Speech-to-Text among 38 products) names Text-to-Speech. The public page shows only broad incidents, so clean is read with that limit (30). Quotas published with numbers, 1,000 requests a minute for most voices, 200 for Chirp 3, 500 for Studio, 100 concurrent streams and 100 long-audio requests a minute (15). The quotas page (last updated 26 October 2026) says nothing about the error a breach returns or how to back off, read as google-speech-to-text was (0). A 99.9 per cent monthly SLA with credits of 10, 25 and 50 per cent, read on 6 November (10). Chirp 3 HD and Gemini 2.5 Flash and Pro TTS are GA, with Gemini 3.1 Flash TTS and Flash-Lite in preview (10). 20 + 30 + 15 + 0 + 10 + 10 = 85.
- 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).

## Score by category

| Category | Weight | Google Cloud Text-to-Speech | Murf TTS API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 85 | 90 | Murf TTS API + MCP +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 85 | Murf TTS API + MCP +5 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 71 | Murf TTS API + MCP +6 |
| Security & auth | 14% (17.5 this run) | 80 | 68 | Google Cloud Text-to-Speech +12 |
| Payments & pricing | 10% (12.5 this run) | 20 | 40 | Murf TTS API + MCP +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 25 | 73 | Murf TTS API + MCP +48 |
| Transparency & trust | 7% (8.8 this run) | 87 | 67 | Google Cloud Text-to-Speech +20 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **66.9 · B** | **69.5 · B** | |

## Facts side by side

| Fact | Google Cloud Text-to-Speech | Murf TTS API + MCP |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Google Cloud | Murf |
| Hosted endpoint | no (local only) | `https://api.murf.ai/v1` |
| Transports | HTTP | HTTP, stdio |
| Auth | OAuth | API key |
| Pricing | Pay per use | Freemium |
| Price for text-to-speech | $10 per 1M tokens | not published |
| x402 | no | no |
| Licence | none | MIT (SDK and MCP server) |
| Tools exposed | 0 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2025-12-30 | 2026-08-20 |
| Terms last updated | 2026-09-02 | no date given |
| Privacy policy last updated | 2026-10-01 | no date given |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 108 stars, 669 PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

## What the same task costs

| Task | Google Cloud Text-to-Speech | Murf TTS API + MCP |
| --- | --- | --- |
| Narrate a 9,000-character script | $0.04 to $1.44 | $0.09 to $0.27 |

## How the scores have moved

### Google Cloud Text-to-Speech

No score change since it was listed.

### Murf TTS API + MCP

- -1.3 on 1 November 2026 (BB to B): product, negative event
- +0.2 on 27 October 2026: checklist
- -0.3 on 8 October 2026: checklist

## Verdicts

**Google Cloud Text-to-Speech.** Cloud TTS has a typed discovery document, a 99.9 per cent SLA, no logging of text or audio, and voices from $4 to $160 per million characters. Its release notes stop at 30 December 2025, the newest Gemini TTS models ship only on the Agent Platform API, and tokens can travel in the URL.

**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

### Google Cloud Text-to-Speech

1. Send OAuth tokens in the Authorization header, never as `access_token` or `key` in the URL
2. Use `synthesizeLongAudio` with a Cloud Storage bucket for long text, and `text:synthesize` for short replies
3. Pick Chirp 3 HD for natural voices with SSML, and Gemini-TTS when the delivery needs prompt steering
4. Check whether the Gemini TTS model you want is on the Cloud TTS API or only on the Agent Platform API
5. Stay within 200 requests a minute on Chirp 3 voices, which have their own quota

### 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, Google Cloud Text-to-Speech or Murf TTS API + MCP?

Murf TTS API + MCP scores 69.5 (B) on agent readiness against Google Cloud Text-to-Speech's 66.9 (B), and leads in 5 of 7 scored categories. Google Cloud Text-to-Speech leads on security & auth and transparency & trust.

### Do Google Cloud Text-to-Speech and Murf TTS API + MCP need an API key?

Google Cloud Text-to-Speech uses an OAuth sign-in. Murf TTS API + MCP needs an API key.

### Can an agent call Google Cloud Text-to-Speech and Murf TTS API + MCP without installing anything?

No hosted endpoint is listed for Google Cloud Text-to-Speech. Murf TTS API + MCP has a hosted endpoint at https://api.murf.ai/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/google-cloud-tts-vs-murf-tts.json, and with the fewest tokens: https://www.anchorterminal.com/compare/google-cloud-tts-vs-murf-tts.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "google-cloud-tts", "b": "murf-tts"}`. From a terminal: `anchor compare google-cloud-tts murf-tts`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/google-cloud-tts.json and https://www.anchorterminal.com/api/v1/tools/murf-tts.json

## Other comparisons with Google Cloud Text-to-Speech or Murf TTS API + MCP

- [Amazon Polly vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/amazon-polly-vs-google-cloud-tts.md)
- [Amazon Polly vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/amazon-polly-vs-murf-tts.md)
- [Azure AI Speech text-to-speech vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts.md)
- [Azure AI Speech text-to-speech vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-murf-tts.md)
- [Cartesia Sonic TTS API + MCP vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/cartesia-tts-vs-google-cloud-tts.md)
- [Cartesia Sonic TTS API + MCP vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/cartesia-tts-vs-murf-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/deepgram-tts-vs-google-cloud-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/deepgram-tts-vs-murf-tts.md)
- [ElevenLabs Text to Speech API + MCP vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-google-cloud-tts.md)
- [ElevenLabs Text to Speech API + MCP vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-murf-tts.md)
- [Fish Audio TTS API vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/fish-audio-tts-vs-google-cloud-tts.md)
- [Fish Audio TTS API vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/fish-audio-tts-vs-murf-tts.md)
- [Google Cloud Text-to-Speech vs HeyGen Voice](https://www.anchorterminal.com/compare/google-cloud-tts-vs-heygen-voice.md)
- [Google Cloud Text-to-Speech vs Inworld Realtime TTS-2](https://www.anchorterminal.com/compare/google-cloud-tts-vs-inworld-tts.md)
- [Google Cloud Text-to-Speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/google-cloud-tts-vs-minimax-speech.md)
- [Google Cloud Text-to-Speech vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts.md)
- [Google Cloud Text-to-Speech vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/google-cloud-tts-vs-resemble-ai-tts.md)
- [Google Cloud Text-to-Speech vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/google-cloud-tts-vs-rime-tts.md)
- [Google Cloud Text-to-Speech vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/google-cloud-tts-vs-smallest-lightning-tts.md)
- [Google Cloud Text-to-Speech vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/google-cloud-tts-vs-soniox-tts.md)
- [HeyGen Voice vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/heygen-voice-vs-murf-tts.md)
- [Inworld Realtime TTS-2 vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/inworld-tts-vs-murf-tts.md)
- [MiniMax Speech (T2A) vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/minimax-speech-vs-murf-tts.md)
- [Murf TTS API + MCP vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/murf-tts-vs-playht-tts.md)
- [Murf TTS API + MCP vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/murf-tts-vs-resemble-ai-tts.md)
- [Murf TTS API + MCP vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/murf-tts-vs-rime-tts.md)
- [Murf TTS API + MCP vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/murf-tts-vs-smallest-lightning-tts.md)
- [Murf TTS API + MCP vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/murf-tts-vs-soniox-tts.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp