Profile-driven MCP server for Google Cloud Text-to-Speech
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"tts-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# tts-mcp Profile-driven MCP server for **Google Cloud Text-to-Speech**: define one profile per app/client so each tool always speaks with the right voice and settings. Exposes three tools to any MCP client: - **`tts_speak`** — synthesize text to audio and auto-play it - **`tts_doctor`** — run diagnostics on auth, profile, and playback - **`tts_stop`** — stop any currently playing audio Voice, language, model, and format are locked per profile — the LLM can only control text content, speaking rate, and pitch. ## Install ```bash pip install tts-mcp ``` Or with [uvx](https://docs.astral.sh/uv/) (no install needed): ```bash uvx tts-mcp --help ``` ## Prerequisites - Python 3.11+ - A [Google Cloud project](https://console.cloud.google.com/freetrial) with the **Cloud Text-to-Speech API** enabled - Google offers a generous free tier — up to **4 million characters/month** for Standard and WaveNet voices, and **1 million characters/month** for Neural2, Polyglot, Chirp 3: HD, and Studio voices, more than enough for most individual use. See [TTS pricing](https://cloud.google.com/text-to-speech/pricing) for details. - [Google Cloud CLI](https://cloud.google.com/sdk/docs/install) (`gcloud`) for authentication - macOS uses `afplay` for playback by default (configurable via profile) ## Setup ### 1. Authenticate with Google Cloud ```bash gcloud auth application-default login gcloud auth application-default set-quota-project YOUR_PROJECT_ID ``` This stores credentials at `~/.config/gcloud/application_default_credentials.json`, which the TTS client discovers automatically. No environment variables needed. ### 2. Create a profiles file ```bash tts-mcp --init ``` This creates a starter config at `~/.config/tts-mcp/profiles.json` with example profiles for every Google TTS voice tier. Edit it to pick your voice, format, and playback settings. The server finds the profiles file automatically — no `--profiles` flag needed for the common case. The search order is: 1. `--…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.