Speak vs LuvVoice Text-to-Speech
Speak is an MCP server published by kaneky.dev. Marketplaces we read that list it: 1 (Official MCP Registry). LuvVoice Text-to-Speech is an MCP server published by franzsy5. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  LuvVoice Text-to-Speech | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 No figure published Not marked · First seen |
Listed Version: 1.0.2 Downloads/month (npm): 173 Downloads/week (npm): 54 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Speak | LuvVoice Text-to-Speech |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (speak.kaneky.dev/mcp) | On your machine (luvvoice-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-23 | 2026-10-15 |
| Endpoint at the last check (differs) | Status out of date: last check 36 h ago returned HTTP 405 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Speak
Text to natural speech as MP3: 38 voices, 7 languages, 1,000 chars per call. Paid per call, x402.
LuvVoice Text-to-Speech
Text-to-speech with 200+ voices in 70+ languages. Requires a LuvVoice API token.
How to run each
Speak As a remote MCP server
claude mcp add --transport http speak https://speak.kaneky.dev/mcpLuvVoice Text-to-Speech As a local MCP server: npm package
claude mcp add --env "LUVVOICE_API_TOKEN=<YOUR_LUVVOICE_API_TOKEN>" --transport stdio luvvoice-mcp -- npx -y luvvoice-mcpRequires: LUVVOICE_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Speak has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Speak publish no settings it asks for, so we do not compare settings.
What it can do: Speak · What it can do: LuvVoice Text-to-Speech · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.