Una integración del Protocolo de Contexto Modelo para Zonos TTS, que permite a Claude generar voz directamente.
Para instalar la integración de Zonos TTS para Claude Desktop automáticamente a través de Smithery :
npx -y @smithery/cli install @PhialsBasement/zonos-tts-mcp --client claudeAsegúrese de tener Zonos ejecutándose con nuestra implementación de API ( PhialsBasement/zonos-api )
Instalar dependencias:
npm install @modelcontextprotocol/sdk axiosConfigurar el acceso a PulseAudio:
# Your pulse audio should be properly configured for audio playback
# The MCP server will automatically try to connect to your pulse serverConstruya el servidor MCP:
npm run build
# This will create the dist folder with the compiled serverAgregar al archivo de configuración de Claude: edite su archivo de configuración de Claude (generalmente en ~/.config/claude/config.json ) y agregue esto a la sección mcpServers :
"zonos-tts": {
"command": "node",
"args": [
"/path/to/your/zonos-mcp/dist/server.js"
]
}Reemplace /path/to/your/zonos-mcp con la ruta real donde instaló el servidor MCP.
Related MCP server: ElevenLabs MCP Server
Una vez configurado, Claude sabe automáticamente cómo utilizar la herramienta speak_response :
speak_response(
text="Your text here",
language="en-us", # optional, defaults to en-us
emotion="happy" # optional: "neutral", "happy", "sad", "angry"
)Texto a voz a través de Claude
Apoyo para múltiples emociones
Soporte multilingüe
Reproducción de audio adecuada a través de PulseAudio
Node.js
Configuración de PulseAudio
Instancia en ejecución de Zonos API (PhialsBasement/zonos-api)
Dispositivo de salida de audio en funcionamiento
Asegúrese de que tanto el servidor API de Zonos como este servidor MCP estén en ejecución
La reproducción de audio requiere una configuración adecuada de PulseAudio
| 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