Eine Model Context Protocol-Integration für Zonos TTS, die es Claude ermöglicht, Sprache direkt zu generieren.
So installieren Sie die Zonos TTS-Integration für Claude Desktop automatisch über Smithery :
npx -y @smithery/cli install @PhialsBasement/zonos-tts-mcp --client claudeStellen Sie sicher, dass Zonos mit unserer API-Implementierung ( PhialsBasement/zonos-api ) ausgeführt wird.
Installieren Sie Abhängigkeiten:
npm install @modelcontextprotocol/sdk axiosKonfigurieren Sie den PulseAudio-Zugriff:
# Your pulse audio should be properly configured for audio playback
# The MCP server will automatically try to connect to your pulse serverErstellen Sie den MCP-Server:
npm run build
# This will create the dist folder with the compiled serverZu Claudes Konfigurationsdatei hinzufügen: Bearbeiten Sie Ihre Claude-Konfigurationsdatei (normalerweise in ~/.config/claude/config.json ) und fügen Sie dies zum Abschnitt mcpServers hinzu:
"zonos-tts": {
"command": "node",
"args": [
"/path/to/your/zonos-mcp/dist/server.js"
]
}Ersetzen Sie /path/to/your/zonos-mcp durch den tatsächlichen Pfad, in dem Sie den MCP-Server installiert haben.
Related MCP server: ElevenLabs MCP Server
Nach der Konfiguration weiß Claude automatisch, wie das Tool speak_response zu verwenden ist:
speak_response(
text="Your text here",
language="en-us", # optional, defaults to en-us
emotion="happy" # optional: "neutral", "happy", "sad", "angry"
)Text-to-Speech durch Claude
Unterstützung mehrerer Emotionen
Mehrsprachige Unterstützung
Korrekte Audiowiedergabe durch PulseAudio
Node.js
PulseAudio-Einrichtung
Ausführen einer Instanz der Zonos-API (PhialsBasement/zonos-api)
Funktionierendes Audioausgabegerät
Stellen Sie sicher, dass sowohl der Zonos-API-Server als auch dieser MCP-Server ausgeführt werden
Für die Audiowiedergabe ist eine ordnungsgemäße PulseAudio-Konfiguration erforderlich.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| language | No | en-us | |
| emotion | No | neutral |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
speak_responseScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'speak_response' stands alone with no other tools to confuse it with, making disambiguation perfect.
Since there is only one tool, naming consistency is inherently perfect. There are no other tools to compare against, so no inconsistencies can exist in the naming pattern.
A single tool for a TTS (Text-to-Speech) server feels thin and under-scoped. TTS typically involves operations like generating, streaming, or managing speech, but this server only offers one tool, which is insufficient for a complete TTS domain coverage.
The server is severely incomplete for a TTS domain. With only a 'speak_response' tool and no description, it lacks essential operations such as configuring voices, controlling speech parameters, or handling different input formats, making it inadequate for typical TTS workflows.
Claude makes real phone calls for you — in many languages, with transcript and outcome back in chat.
Transcribe audio and video with Speechmatics speech-to-text from Claude and any MCP client.
Speech, transcription, voice agents, Trace, Recap, dubbing and narration with browser OAuth.
ElevenLabs in natural language: generate speech in any language, create and manage voices, compose m