Advanced TTS MCP Server
Related Servers
Alternatives to Advanced TTS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables real-time voice agents to dynamically modulate speech pitch, cadence, and pause inflections via prosody, SSML, and emotion pacing for low-latency conversational audio.7-
- FlicenseNot gradedqualityBmaintenanceEnables real-time voice agents to dynamically tailor speech pitch, cadence, and pause inflections through low-latency prosody, SSML, and emotion pacing modulation.7-
- AlicenseAqualityAmaintenanceGive your AI agent a voice with x402 pay-per-call speech synthesis, offering 20 voices, 10 personas, 31 languages, and granular controls.657 npmMIT

leanvox-mcpofficial
AlicenseNot gradedqualityDmaintenanceEnables text-to-speech generation, voice cloning, dialogue creation, and other TTS operations through natural language in MCP-compatible AI assistants.12 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables natural language generation of speech in any language, voice creation and management, music composition, dubbing, pronunciation dictionaries, and account history/usage through any MCP client using your own API key.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to convert text to speech using Microsoft Edge's Text-to-Speech service with customizable voice options, speech rate, volume, and pitch parameters.MIT
TDQS
Scored across 5 tools
Each tool has a distinct, non-overlapping purpose: batch_synthesize handles multiple segments, synthesize_speech handles single conversions, get_status checks request status, get_voices lists voice options, and list_output_files manages saved files. The descriptions clearly differentiate their functions, eliminating ambiguity.
All tools follow a consistent verb_noun naming pattern (e.g., batch_synthesize, get_status, get_voices, list_output_files, synthesize_speech). The verbs (batch_, get_, list_, synthesize_) are appropriate and uniform, making the set predictable and easy to understand.
With 5 tools, the server is well-scoped for a TTS (text-to-speech) domain. The count is appropriate, covering core operations like synthesis, status checking, voice management, and file listing without being too sparse or bloated. Each tool earns its place in the workflow.
The tool set covers essential TTS operations: synthesis (single and batch), status tracking, voice discovery, and output management. A minor gap exists in lacking explicit tools for deleting or managing output files beyond listing, but agents can likely work around this, and core workflows are well-supported.