A
licenseB
qualityD
maintenanceEnables natural language-driven speech synthesis using Fish Audio's Text-to-Speech API, supporting multiple voices, streaming, and flexible configuration.
2
17
MIT
mcp-loudkit
Officialby loudreader
Related Servers
Alternatives to mcp-loudkit
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to speak aloud by generating and playing audio through the system output. Supports multiple TTS providers, playback queue management, and configurable voice profiles.131MIT
- FlicenseNot gradedqualityBmaintenanceLocal multilingual TTS (24 languages incl. Ukrainian) with zero-shot voice cloning, voice design, and speech editing via HTTP API and MCP server.4-
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to synthesize natural speech using either platform system voices or premium OpenAI TTS, with automatic engine selection and graceful fallback.118MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to speak by running local voice models using Chatterbox Turbo TTS or Kokoro TTS, with support for voice cloning, paralinguistic tags, and multiple voices.7313MIT
- AlicenseAqualityAmaintenanceText-to-speech MCP server that enables AI assistants to read text aloud on the user's computer using Windows SAPI, with no API key or cloud service required.11MIT
- AlicenseNot gradedqualityBmaintenanceLocal MCP server for neural text-to-speech using Kokoro ONNX engine on CPU, supporting SSML tags, multiple voice profiles, and zero-GPU operation for low-latency speech synthesis.32MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA local voice interface providing high-performance speech recognition and natural text-to-speech with voice cloning capabilities. It enables AI assistants to speak, listen, and engage in character-based voice conversations through integrated MCP tools.-
- AlicenseAqualityBmaintenanceEnables MCP clients to synthesize text into speech locally and play it through the machine's audio, with selectable voices and playback speed.2Apache 2.0
TDQS
A4.2/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct responsibility: listing available voices, performing synthesis, and reporting configuration details. There is no overlap or ambiguity between their purposes.
Naming Consistency4/5
All tool names are lowercase imperative verbs, but list_voices follows a verb_noun pattern while synthesize and describe are standalone verbs. The naming is still readable and predictable, with only a minor structural inconsistency.
Tool Count5/5
Three tools is well-scoped for a text-to-speech server: discover voices, synthesize speech, and inspect configuration. Each tool earns its place without redundancy or bloat.
Completeness5/5
The surface covers the full core workflow: discovering available voices, generating audio from text, and inspecting the active configuration for debugging. No major gaps are apparent for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues