MCP server for the SpeakGlobal Developer API (/v1).
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":"speak-global-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.
# speak-global-mcp Connect desktop AI apps and editors that support the **Model Context Protocol** (MCP) to [SpeakGlobal](https://speakglobal.ai): voice-style TTS, recordings, transcription, and audio processing via the same **Developer API** (`/v1`) as your dashboard key (**Account → Developer**). | | | |--|--| | **Install** | [PyPI: `speak-global-mcp`](https://pypi.org/project/speak-global-mcp/) — `pip install` / `pipx install` | | **Source & issues** | [github.com/Design-Aura/speak-global-MCP](https://github.com/Design-Aura/speak-global-MCP) | **Limits:** Export billing APIs are not exposed as MCP tools (`/v1/tts/export`, export-status, `/v1/recordings/export`). --- ## Requirements - **Python 3.10+** - A **SpeakGlobal Developer API key** (`sg_live_…`) from the dashboard --- ## Install ### From PyPI (recommended) **pipx** (keeps dependencies separate — good for CLI-style tools): ```bash pipx install speak-global-mcp pipx ensurepath ``` Open a **new** terminal so `speakglobal-mcp` is on your `PATH`. Pin a version if you want (see [PyPI versions](https://pypi.org/project/speak-global-mcp/#history)): ```bash pipx install "speak-global-mcp==X.Y.Z" ``` **venv + pip:** ```bash python -m venv .venv .venv\Scripts\activate # Windows # source .venv/bin/activate # macOS / Linux pip install speak-global-mcp ``` --- ## Connect an MCP client This server speaks MCP over **stdio**: your app starts `speakglobal-mcp` (or `python -m speak_global_mcp.server`) **locally**. Put the API key only in that app’s config — never commit it. Most clients use the same shape: a top-level **`mcpServers`** object with one entry per server: **`command`**, optional **`args`**, and **`env`** for `SPEAKGLOBAL_*`. Use **`SPEAKGLOBAL_ENVIRONMENT=production`** with the live API (HTTPS + non-empty key). Restart or reload MCP in the app after editing config. ### Example: `speakglobal-mcp` on `PATH` (after pipx) ```json { "mcpServers": { "speakglobal": { "com…
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.