Blabber-MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Blabber-MCP read this text aloud with the shimmer voice"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
📢 Blabber-MCP 🗣️
An MCP server that gives your LLMs a voice using OpenAI's Text-to-Speech API! 🔊
✨ Features
Text-to-Speech: Converts input text into high-quality spoken audio.
Voice Selection: Choose from various OpenAI voices (
alloy,echo,fable,onyx,nova,shimmer).Model Selection: Use standard (
tts-1) or high-definition (tts-1-hd) models.Format Options: Get audio output in
mp3,opus,aac, orflac.File Saving: Saves the generated audio to a local file.
Optional Playback: Automatically play the generated audio using a configurable system command.
Configurable Defaults: Set a default voice via configuration.
Related MCP server: NijiVoice-MCP
🔧 Configuration
To use this server, you need to add its configuration to your MCP client's settings file (e.g., mcp_settings.json).
Get OpenAI API Key: You need an API key from OpenAI.
Add to MCP Settings: Add the following block to the
mcpServersobject in your settings file, replacing"YOUR_OPENAI_API_KEY"with your actual key.
{
"mcpServers": {
"blabber-mcp": {
"command": "node",
"args": ["/full/path/to/blabber-mcp/build/index.js"], (IMPORTANT: Use the full, absolute path to the built index.js file)
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY",
"AUDIO_PLAYER_COMMAND": "xdg-open", (Optional: Command to play audio (e.g., "cvlc", "vlc", "mpv", "ffplay", "afplay", "xdg-open"; defaults to "cvlc")
"DEFAULT_TTS_VOICE": "nova" (Optional: Set default voice (alloy, echo, fable, onyx, nova, shimmer); defaults to nova)
},
"disabled": false,
"alwaysAllow": []
}
}
}Important: Make sure the args path points to the correct location of the build/index.js file within your blabber-mcp project directory. Use the full absolute path.
🚀 Usage
Once configured and running, you can use the text_to_speech tool via your MCP client.
Tool: text_to_speech
Server: blabber-mcp (or the key you used in the config)
Arguments:
input(string, required): The text to synthesize.voice(string, optional): The voice to use (alloy,echo,fable,onyx,nova,shimmer). Defaults to theDEFAULT_TTS_VOICEset in config, ornova.model(string, optional): The model (tts-1,tts-1-hd). Defaults totts-1.response_format(string, optional): Audio format (mp3,opus,aac,flac). Defaults tomp3.play(boolean, optional): Set totrueto automatically play the audio after saving. Defaults tofalse.
Example Tool Call (with playback):
<use_mcp_tool>
<server_name>blabber-mcp</server_name>
<tool_name>text_to_speech</tool_name>
<arguments>
{
"input": "Hello from Blabber MCP!",
"voice": "shimmer",
"play": true
}
</arguments>
</use_mcp_tool>Output:
The tool saves the audio file to the output/ directory within the blabber-mcp project folder and returns a JSON response like this:
{
"message": "Audio saved successfully. Playback initiated using command: cvlc",
"filePath": "path/to/speech_1743908694848.mp3",
"format": "mp3",
"voiceUsed": "shimmer"
}📜 License
This project is licensed under the MIT License - see the LICENSE file for details.
🕒 Changelog
See the CHANGELOG.md file for details on version history.
Available Tools
1 tooltext_to_speechA
Converts text into spoken audio using OpenAI TTS (default voice: alloy), saves it to a file, and optionally plays it.
Inputs: input (required), model, play, response_format, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clearly distinct purpose of converting text to speech, and no other tools exist to cause confusion.
The single tool name 'text_to_speech' follows a clear verb_noun pattern (text_to_speech), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for most server purposes, as it severely limits functionality and scope. While the tool itself is well-defined, the server lacks breadth, making it feel thin and under-scoped for typical MCP use cases.
The server is severely incomplete for a text-to-speech domain. It only provides conversion to speech, with no tools for managing audio files (e.g., list, delete, play controls), voice selection beyond the default, or other related operations like speech-to-text, leading to significant gaps in coverage.
Maintenance
Related MCP Connectors
AI voice generation: text-to-speech and voice cloning from any MCP client.
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
MCP server exposing the AceDataCloud Fish Audio API (text-to-speech with voice conditioning)
MCP server for Text-to-Speech
Related MCP Servers
- AlicenseBqualityDmaintenanceA MCP server that enables transcription of audio files using OpenAI's Speech-to-Text API, with support for multiple languages and file saving options.12 npm10MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables LLMs to access the NijiVoice API for text-to-speech generation, supporting features like fetching available voice actors and checking credit balance.32MIT
- FlicenseCqualityCmaintenanceAn MCP server that exposes speech-to-text and text-to-speech capabilities using a local speaches instance, allowing AI assistants to transcribe audio and generate speech.2-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides text-to-speech, speech-to-text, and voice management via ElevenLabs API.1MIT