Skip to main content
Glama
PhialsBasement

Zonos TTS MCP Server

Zonos MCP 集成

铁匠徽章

Zonos TTS 的模型上下文协议集成,允许 Claude 直接生成语音。

设置

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 Zonos TTS Integration:

npx -y @smithery/cli install @PhialsBasement/zonos-tts-mcp --client claude

手动安装

  1. 确保您已使用我们的 API 实现 ( PhialsBasement/zonos-api ) 运行 Zonos

  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 一起使用

配置完成后,Claude 自动知道如何使用speak_response工具:

speak_response(
    text="Your text here",
    language="en-us",  # optional, defaults to en-us
    emotion="happy"    # optional: "neutral", "happy", "sad", "angry"
)

特征

  • 通过 Claude 进行文本转语音

  • 多种情绪支持

  • 多语言支持

  • 通过 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