Zonos TTS MCP Server
Zonos MCP統合
Zonos TTS のモデル コンテキスト プロトコル統合により、Claude は直接音声を生成できるようになります。
設定
Smithery経由でインストール
Smithery経由で Claude Desktop 用の Zonos TTS 統合を自動的にインストールするには:
npx -y @smithery/cli install @PhialsBasement/zonos-tts-mcp --client claude手動インストール
Zonos が API 実装 ( PhialsBasement/zonos-api ) で実行されていることを確認してください。
依存関係をインストールします:
npm install @modelcontextprotocol/sdk axiosPulseAudio アクセスを構成します。
# Your pulse audio should be properly configured for audio playback
# The MCP server will automatically try to connect to your pulse serverMCP サーバーを構築します。
npm run build
# This will create the dist folder with the compiled serverClaude の設定ファイルに追加します。Claude の設定ファイル (通常は
~/.config/claude/config.jsonにあります) を編集し、mcpServersセクションに以下を追加します。
"zonos-tts": {
"command": "node",
"args": [
"/path/to/your/zonos-mcp/dist/server.js"
]
}/path/to/your/zonos-mcp MCP サーバーをインストールした実際のパスに置き換えます。
Related MCP server: ElevenLabs MCP Server
クロードと一緒に使う
一度設定すると、Claude はspeak_responseツールの使い方を自動的に認識します。
speak_response(
text="Your text here",
language="en-us", # optional, defaults to en-us
emotion="happy" # optional: "neutral", "happy", "sad", "angry"
)特徴
クロードによるテキスト読み上げ
多様な感情のサポート
多言語サポート
PulseAudioによる適切なオーディオ再生
要件
Node.js
PulseAudioのセットアップ
Zonos API の実行中のインスタンス (PhialsBasement/zonos-api)
動作するオーディオ出力デバイス
注記
Zonos APIサーバーとこのMCPサーバーの両方が実行中であることを確認してください
オーディオ再生には適切なPulseAudio設定が必要です
Available Tools
1 toolspeak_responseD
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| language | No | en-us | |
| emotion | No | neutral |
TDQS
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
speak_response
TDQS
Scored 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.
Maintenance
Related MCP Connectors
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
Related MCP Servers
- AlicenseDqualityDmaintenanceProvides text-to-speech capabilities through the Model Context Protocol, allowing applications to easily integrate speech synthesis with customizable voices, adjustable speech speed, and cross-platform audio playback support.110MIT
- AlicenseNot gradedqualityDmaintenanceOfficial ElevenLabs Model Context Protocol server that enables AI assistants like Claude to interact with Text to Speech and audio processing APIs, allowing them to generate speech, clone voices, transcribe audio, and create soundscapes.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables voice-based interactions with Claude by converting text to speech using Kokoro TTS and transcribing user responses using NVIDIA NeMo ASR, creating interactive voice dialogues.MIT
- AlicenseNot gradedqualityDmaintenanceProvides text-to-speech generation using the Kokoro-82M model, enabling AI assistants to generate voiceovers and audio content directly within Claude Desktop and Cursor.14Apache 2.0