speak vs Narrivela
speak is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
speak is a plugin bundle for AI coding tools published by Guillermo Weinmann. No marketplace we read lists it any more. Narrivela is an MCP server published by narrivela.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace alphabet/speak | Removed on 2026-10-17 Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.0 No figure published 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 | speakno longer listed · | Narrivela |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (app.narrivela.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/alphabet/speak | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-13 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of speak
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Give Claude Code a voice with multi-engine text-to-speech. Speaks responses aloud using 5 TTS engines (edge-tts, ElevenLabs, Kokoro, macOS say, espeak-ng). Free by default…
-
This skill converts text to high-quality audio files using ElevenLabs API. Use this skill when users request text-to-spe
-
Reads text aloud locally on Windows, macOS, and Linux. No API key, account, or cloud service.
-
Speaks a voice-cloned summary when Claude finishes deep work. Works out of the box with bundled voice, or clone your own. Triggers on long responses, multiple tool calls, or…
-
Voice mode for Claude Code: reads assistant replies aloud (TTS) with auto language detection (de/en) and optional summarization. Also provides the WhatsApp / Telegram / Discord…
-
Add Grok voice to an app: realtime speech-to-speech, speech-to-text dictation, text-to-speech read-aloud, and a log-driven fix loop for voice sessions.
What each says it does
speak
Text-To-Speech synthesizer for Claude Code
Narrivela
Generate English and Chinese speech, split long text, track batch jobs, and download audio.
How to run each
speak
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Narrivela As a remote MCP server
claude mcp add --transport http narrivela https://app.narrivela.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Narrivela 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
Neither one's marketplaces publish the settings it asks for.
What it can do: speak · What it can do: Narrivela · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.