# ElevenLabs Text to Speech API + MCP vs Google Cloud Text-to-Speech

> ElevenLabs Text to Speech scores 75.3 (BB) 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/elevenlabs-tts-vs-google-cloud-tts
- Markdown: https://www.anchorterminal.com/compare/elevenlabs-tts-vs-google-cloud-tts.md (~5,650 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

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

- ElevenLabs Text to Speech API + MCP: grade BB, 75.3/100, rank #67 of 1510. Markdown https://www.anchorterminal.com/tools/elevenlabs-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/elevenlabs-tts.json
- Google Cloud Text-to-Speech: grade B, 66.9/100, rank #351 of 1510. Markdown https://www.anchorterminal.com/tools/google-cloud-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/google-cloud-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

### ElevenLabs Text to Speech API + MCP (BB)

Good 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 80
- Agent ergonomics, 92 against 65
- Payments & pricing, 40 against 20
- Maintenance & community, 77 against 25

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Runs on your own machine

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

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

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

Ahead on:
- Reliability, 85 against 80
- Security & auth, 80 against 65
- Transparency & trust, 87 against 68

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


## Why the edge

### Maintenance & community: ElevenLabs Text to Speech API + MCP +52

- ElevenLabs Text to Speech API + MCP (77): Read as a model. Newest release is SDK 2.75.0, tagged in both the Python and JavaScript repositories on 27 October 2026 (23:02 UTC) and listed in the 26 October changelog entry, which also added `clone_strength` to Text to Speech (30). Weekly dated entries, 16 between 3 August and 26 October (10). Turbo v2 and v2.5 are still marked deprecated in favour of Flash with no dates or notice period, v3 and Multilingual v2 are labelled previous generation without a retirement date, and the 26 October entry deprecates `use_pvc_as_ivc` on Text to Dialogue and the `/v1/speech-to-speech` paths without a removal date (0 of 10). Public changelog and support channels (10 of 15). The Python SDK had 19 open issues on 1 October, several opened in August 2026, not re-read on 17 October or 1 November (5 of 10). Official Python and TypeScript SDKs current at 2.75.0, with 3.0.0-alpha.1 tagged (15). Fern-generated SDK with an open issue about a blank changelog, per the 1 October check (7 of 10). 30 + 10 + 0 + 10 + 5 + 15 + 7 = 77.
- 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.

### Agent ergonomics: ElevenLabs Text to Speech API + MCP +27

- 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).
- 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.

### Payments & pricing: ElevenLabs Text to Speech API + MCP +20

- ElevenLabs Text to Speech API + MCP (40): No x402, MPP or L402 (0). Per-1,000-character prices for every model published without a login, re-read on 1 November, $0.08 on v4, v3 and Multilingual v2 and $0.04 on v4 Turbo, v3 Conversational and Flash (20). Free plan with 10,000 v4 characters a month and no card, per the 5 October check. The pricing page read on 1 November lists card, Apple Pay and Google Pay for paid subscriptions and doesn't say the free plan needs one (20). A person signs up in a browser (0). 0 + 20 + 20 + 0 = 40.
- 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.

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

- ElevenLabs Text to Speech API + MCP (68): Closed service with clear terms and MIT SDKs (15). The Terms and Privacy Policy (both updated 9 October 2026, re-read on 1 November) allow training on content with a forward-only opt-out under Data use, while the Eleven v4 launch page, re-read on 1 November, still says scripts and audio tags aren't used for training without consent, and the zero-retention page says only that third-party LLM providers don't train on customer content. The statements don't agree (10). Deprecated models and parameters are marked on the models page and in the changelog without dates or a written policy (5). EU, India and Singapore residency hosts documented, no named sub-processor list found (15). 15 + 10 + 5 + 15 = 45.
- 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.

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

- ElevenLabs Text to Speech API + MCP (65): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys can be restricted to chosen endpoints, given a credit quota and limited to IP addresses or CIDR ranges, the docs walk through rotation, service accounts hold keys that don't belong to a person, and user keys and (since 26 October) service account keys can be set to expire (30). The Terms (updated 9 October 2026, re-read on 1 November) still let ElevenLabs use content to improve its models, with an opt-out under Data use in account settings that only applies going forward (10). TTS text and audio are kept by default and zero retention through `enable_logging=false` is Enterprise only (5). The generation history lists each request, though we found no audit log of key actions (10 of 15). A valid security.txt (expiring 6 October 2027, re-read on 1 November) pointing to a report form, and the Eleven v4 launch page states SOC 2 Type II, ISO 27001 and PCI DSS Level 1 certification. We count those as vendor claims because we saw no report, and the trust centre wasn't re-read. No bug bounty or public advisories found (10). 30 + 10 + 5 + 10 + 10 = 65.
- 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.

### Schema & documentation: ElevenLabs Text to Speech API + MCP +14

- 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.
- Google Cloud Text-to-Speech (80): Discovery document revision 20260827 with typed methods and 26 schemas, and protocol buffers for gRPC (25). No llms.txt found (0). The Chirp 3 HD and Gemini-TTS pages say which voices suit which use and list formats and limits, but the reference doesn't say when to choose streaming or long audio (15 of 20). Typed messages with enums for encoding and gender and required fields (15). Samples in several languages, standard status codes with little method-specific error detail (10 of 15). Versioned v1 and v1beta1 with dated release notes (15). Total 80.

## Score by category

| Category | Weight | ElevenLabs Text to Speech API + MCP | Google Cloud Text-to-Speech | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 85 | Google Cloud Text-to-Speech +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 94 | 80 | ElevenLabs Text to Speech API + MCP +14 |
| Agent ergonomics | 13% (16.2 this run) | 92 | 65 | ElevenLabs Text to Speech API + MCP +27 |
| Security & auth | 14% (17.5 this run) | 65 | 80 | Google Cloud Text-to-Speech +15 |
| Payments & pricing | 10% (12.5 this run) | 40 | 20 | ElevenLabs Text to Speech API + MCP +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 77 | 25 | ElevenLabs Text to Speech API + MCP +52 |
| Transparency & trust | 7% (8.8 this run) | 68 | 87 | Google Cloud Text-to-Speech +19 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **75.3 · BB** | **66.9 · B** | |

## Facts side by side

| Fact | ElevenLabs Text to Speech API + MCP | Google Cloud Text-to-Speech |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | ElevenLabs | Google Cloud |
| Hosted endpoint | `https://api.elevenlabs.io/v1` | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| Price for text-to-speech | not published | $10 per 1M tokens |
| x402 | no | no |
| Licence | MIT (SDKs) | none |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | `io.elevenlabs/mcp` | not listed |
| Last release | 2026-10-27 | 2025-12-30 |
| Terms last updated | 2026-03-31 | 2026-09-02 |
| Privacy policy last updated | 2026-05-20 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 3.1k stars, 1.1M npm/wk, 2.2M PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | none |

## What the same task costs

| Task | ElevenLabs Text to Speech API + MCP | Google Cloud Text-to-Speech |
| --- | --- | --- |
| Narrate a 9,000-character script | $0.36 to $0.72 | $0.04 to $1.44 |

## How the scores have moved

### ElevenLabs Text to Speech API + MCP

- +0.1 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist
- +2.3 on 6 October 2026: new evidence

### Google Cloud Text-to-Speech

No score change since it was listed.

## 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.

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

## 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.

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

## Questions

### Which is better for AI agents, ElevenLabs Text to Speech API + MCP or Google Cloud Text-to-Speech?

ElevenLabs Text to Speech API + MCP scores 75.3 (BB) on agent readiness against Google Cloud Text-to-Speech's 66.9 (B), and leads in 4 of 7 scored categories. Google Cloud Text-to-Speech leads on reliability, security & auth and transparency & trust.

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

ElevenLabs Text to Speech API + MCP takes an API key or an OAuth sign-in. Google Cloud Text-to-Speech uses an OAuth sign-in.

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

ElevenLabs Text to Speech API + MCP has a hosted endpoint at https://api.elevenlabs.io/v1. No hosted endpoint is listed for Google Cloud Text-to-Speech.


## For agents

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

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

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

---

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