Skip to main content
Glama
PhialsBasement

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

手動インストール

  1. Zonos が API 実装 ( PhialsBasement/zonos-api ) で実行されていることを確認してください。

  2. 依存関係をインストールします:

npm install @modelcontextprotocol/sdk axios
  1. PulseAudio アクセスを構成します。

# Your pulse audio should be properly configured for audio playback
# The MCP server will automatically try to connect to your pulse server
  1. MCP サーバーを構築します。

npm run build
# This will create the dist folder with the compiled server
  1. Claude の設定ファイルに追加します。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 tool
speak_responseD
ParametersJSON Schema
NameRequiredDescriptionDefault
textYes
languageNoen-us
emotionNoneutral

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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. 1 tool update
    • First observedspeak_response

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness1/5

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

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers