Skip to main content
Glama
PhialsBasement

Zonos TTS MCP Server

Zonos MCP 통합

대장간 배지

Claude가 직접 음성을 생성할 수 있도록 하는 Zonos TTS에 대한 모델 컨텍스트 프로토콜 통합.

설정

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 Zonos TTS 통합을 자동으로 설치하려면:

지엑스피1

수동 설치

  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를 통한 적절한 오디오 재생

요구 사항

  • 노드.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