A
licenseB
qualityD
maintenanceA MCP server that enables transcription of audio files using OpenAI's Speech-to-Text API, with support for multiple languages and file saving options.
1
1 npm
10
MIT
Blabber-MCP
📢 Blabber-MCP 🗣️
Ein MCP-Server, der Ihren LLMs mithilfe der Text-to-Speech-API von OpenAI eine Stimme verleiht! 🔊
✨ Funktionen
Text-to-Speech: Wandelt Eingabetext in hochwertiges gesprochenes Audio um.
Stimmwahl: Wählen Sie aus verschiedenen OpenAI-Stimmen (
alloy,echo,fable,onyx,nova,shimmer).Modellwahl: Verwenden Sie Standard- (
tts-1) oder High-Definition-Modelle (tts-1-hd).Formatoptionen: Erhalten Sie Audioausgaben in
mp3,opus,aacoderflac.Speichern von Dateien: Speichert das generierte Audio in einer lokalen Datei.
Optionale Wiedergabe: Spielt das generierte Audio automatisch über einen konfigurierbaren Systembefehl ab.
Konfigurierbare Standardwerte: Legen Sie eine Standardstimme über die Konfiguration fest.
Related MCP server: NijiVoice-MCP
🔧 Konfiguration
Um diesen Server zu verwenden, müssen Sie seine Konfiguration zur Einstellungsdatei Ihres MCP-Clients hinzufügen (z. B. mcp_settings.json).
OpenAI API-Schlüssel abrufen: Sie benötigen einen API-Schlüssel von OpenAI.
Zu MCP-Einstellungen hinzufügen: Fügen Sie den folgenden Block zum
mcpServers-Objekt in Ihrer Einstellungsdatei hinzu und ersetzen Sie"YOUR_OPENAI_API_KEY"durch Ihren tatsächlichen Schlüssel.
{
"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": []
}
}
}Wichtig: Stellen Sie sicher, dass der args-Pfad auf den korrekten Speicherort der build/index.js-Datei innerhalb Ihres blabber-mcp-Projektverzeichnisses zeigt. Verwenden Sie den vollständigen absoluten Pfad.
🚀 Verwendung
Sobald er konfiguriert ist und läuft, können Sie das text_to_speech-Tool über Ihren MCP-Client verwenden.
Tool: text_to_speech
Server: blabber-mcp (oder der Schlüssel, den Sie in der Konfiguration verwendet haben)
Argumente:
input(Zeichenfolge, erforderlich): Der zu synthetisierende Text.voice(Zeichenfolge, optional): Die zu verwendende Stimme (alloy,echo,fable,onyx,nova,shimmer). Standardmäßig wird die in der Konfiguration festgelegteDEFAULT_TTS_VOICEodernovaverwendet.model(Zeichenfolge, optional): Das Modell (tts-1,tts-1-hd). Standard isttts-1.response_format(Zeichenfolge, optional): Audioformat (mp3,opus,aac,flac). Standard istmp3.play(boolesch, optional): Auftruesetzen, um das Audio nach dem Speichern automatisch abzuspielen. Standard istfalse.
Beispiel für einen Tool-Aufruf (mit Wiedergabe):
<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>Ausgabe:
Das Tool speichert die Audiodatei im output/-Verzeichnis innerhalb des blabber-mcp-Projektordners und gibt eine JSON-Antwort wie diese zurück:
{
"message": "Audio saved successfully. Playback initiated using command: cvlc",
"filePath": "path/to/speech_1743908694848.mp3",
"format": "mp3",
"voiceUsed": "shimmer"
}📜 Lizenz
Dieses Projekt ist unter der MIT-Lizenz lizenziert – siehe die Datei LICENSE für Details.
🕒 Änderungsprotokoll
Siehe die Datei CHANGELOG.md für Details zur Versionsgeschichte.
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | The text to synthesize into speech. | |
| model | No | The TTS model to use. | tts-1 |
| play | No | Whether to automatically play the generated audio file. | |
| response_format | No | The format of the audio response. | mp3 |
| voice | No | Optional: The voice to use. Overrides the configured default (alloy). |
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that audio is saved to a file and optionally played, which covers some output behavior, but lacks details on file location, naming, permissions, error handling, rate limits, or authentication needs. For a tool with no annotations, this leaves significant gaps in understanding its operational traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that efficiently conveys the core functionality, default settings, and optional features without any wasted words. It's front-loaded with the primary purpose and includes all necessary details concisely.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (5 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and some behavioral aspects (saving and playing), but lacks details on output format, error handling, and other operational context that would be helpful for an agent to use it effectively without annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning the default voice (alloy) and the optional play feature, but doesn't provide additional syntax, format, or usage context for parameters. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('Converts text into spoken audio'), identifies the resource ('using OpenAI TTS'), and provides implementation details ('saves it to a file, and optionally plays it'). It distinguishes itself by mentioning the default voice (alloy) and the optional play feature, which would be relevant if there were sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage through the phrase 'optionally plays it,' suggesting when the play parameter might be used, but provides no explicit guidance on when to use this tool versus alternatives (though none are listed as siblings). There's no mention of prerequisites, limitations, or specific scenarios for choosing different models or voices.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
text_to_speech
TDQS
A3.5/5.0
Scored across 1 tool
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count2/5
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.
Completeness2/5
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
ActivityInactive
ResponsivenessNo issues
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
- 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-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that provides text-to-speech, speech-to-text, and voice management via ElevenLabs API.1-