mcp-speak
Related Servers
Alternatives to mcp-speak
AlicenseAqualityBmaintenanceConnects Speak AI transcription and insight data to Claude and ChatGPT, enabling natural language queries for summaries, action items, and quotes from recordings.1002,451 npmMIT- 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.10 npm1MIT
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.17 npmMIT
- 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
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to generate and play high-quality text-to-speech audio using the Kokoro model, with support for multiple voices, adjustable speaking speed, and audio caching.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to give spoken output by synthesizing text into speech with an on-device neural model and playing it through the user's speakers, entirely offline. Agents can queue spoken summaries and stop playback on demand.2 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to speak aloud using text-to-speech functionality. Works with agents running inside devcontainers and provides configurable voice settings for creating chatty AI companions.6-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to speak text aloud on macOS using the built-in say command, with no external speech API or keys, and to list available voices and control rate or voice selection. Requests from multiple client threads share a single FIFO playback worker, so speech plays one item at a time and can be inspected, stopped, or muted in hold or discard mode.3 npmMIT
TDQS
Scored across 2 tools
The two tools perform the same core action but are clearly differentiated by blocking behavior, with descriptive names and explicit notes in the descriptions. There is some overlap in purpose, but the distinction is obvious enough for an agent to select correctly.
Both tool names follow a consistent verb-first pattern with a modifier suffix (speak, speak_non_blocking). Naming clearly conveys the difference without mixing conventions or vague verbs.
Two tools is well-scoped for a text-to-speech server with blocking and non-blocking variants. Every tool earns its place, and the count matches the narrow purpose.
The server provides both blocking and non-blocking speech synthesis, covering the primary use cases. Minor gaps like canceling playback or selecting voices exist, but they are optional for the core domain.