kokoro-tts-mcp
Related Servers
Alternatives to kokoro-tts-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets an AI assistant turn written text — or prose it writes itself — into narrated audiobooks with chapter-marked .m4b files, using local Kokoro voices entirely offline and free. It supports 54 voices across 9 languages, adjustable speed, voice blending, and chapter-level resumable rendering.31 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceEnables text-to-speech conversion using the Kokoro TTS model, running fully locally with native JavaScript. Supports multiple voices, speed control, and integrates with MCP-compatible clients.14 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude, Cursor and VS Code to synthesize speech locally in 31 languages, saving mp3, wav or ogg files, listing and installing catalog voices, and playing audio back through the system player — offline after the first run with no usage limits.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to narrate internal thoughts, announce tool actions, and speak final responses aloud through local cross-platform text-to-speech. It exposes dedicated audio tools over stdio JSON-RPC for MCP-compatible clients.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to generate local, offline text-to-speech audio in 31 languages, manage and install voices, and save or play audio files.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local MCP server that turns any text into narration, voice-overs, dialogues, audiobook chapters and per-shot video clips as MP3/WAV files — with emotions, acting modes, inline cues, presets and subtitles — driven by a ChatGPT sign-in rather than an API key. It also exposes tools for inspecting audio (timings, pace, pitch, waveform), transcribing recordings, listing and favouring voices, saving pronunciation presets, and checking sign-in status.MIT
TDQS
Scored across 2 tools
The two tools have clearly separate purposes: tts_config manages settings (enable/disable, auto-speak, voice, speed) while speak performs text-to-speech playback. Descriptions explicitly cross-reference each other, so an agent can trivially choose the right tool.
Both names are lowercase snake_case, but tts_config is a noun-style resource name while speak is a bare verb, a minor deviation from a single convention. With only two tools the pattern remains readable and predictable.
Two tools is on the light side, but the server's scope is narrow (local TTS playback plus configuration), and both tools earn their place without redundancy. Slightly thin if one expected richer voice management, but reasonable overall.
Configuration covers the key lifecycle controls (enable/disable, auto-speak, voice, speed) and speak handles playback with clear guidance on when to invoke it. Minor gaps like listing available voices or pausing/stopping mid-utterance are handled indirectly via disabling TTS.