SpeechLab MCP
Related Servers
Alternatives to SpeechLab MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage voices and generate speech, multi-character dubbing, and batch audio through a local TTS service, including health checks and job polling.Apache 2.0
- AlicenseBqualityCmaintenanceEnables MCP clients to synthesize local speech, emotional narration, reference-timbre cloning, and singing from text or phoneme/MIDI/duration inputs using installed VoxCPM2 and SoulX-Singer models.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables text-to-speech generation using ten built-in voices and saves the resulting audio as a local WAV file.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to generate local GPU-accelerated narration audio from text, with tools for speech generation, job continuation, and model or voice queries.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to generate narration in a single fixed, pre-approved voice, returning audio with per-line timing, hashes, and automatic quality checks on content, speaker identity, and pace, all locally and reproducibly.-

leanvox-mcpofficial
AlicenseNot gradedqualityDmaintenanceEnables text-to-speech generation, voice cloning, dialogue creation, and other TTS operations through natural language in MCP-compatible AI assistants.20 npmMIT
TDQS
Scored across 4 tools
list_providers and provider_status overlap substantially since list_providers already reports health, making the dedicated health-check largely redundant and easy to misselect. list_voices and synthesize are clearly distinct, so the overlap is confined to two tools.
Three tools use verb_noun (list_providers, list_voices) or bare verb (synthesize), while provider_status uses a noun_noun form, breaking the pattern. Mixed conventions but still readable.
Four tools is on the lean side but appropriate for a focused TTS server: provider discovery, health, voices, and synthesis. The only inefficiency is the split between list_providers and provider_status, which could be consolidated.
The core TTS lifecycle (discover providers, list voices, synthesize to WAV) is well covered. Minor gaps exist around listing/managing generated audio files or configuring providers, but agents can work around these.