Skip to main content
Glama
enesjakozh
giannisanni

Kokoro TTS MCP Server

by giannisanni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Kokoro TTS MCP 服务器

一个模型上下文协议 (MCP) 服务器，使用 Kokoro TTS 引擎提供文本转语音功能。该服务器通过 MCP 工具提供 TTS 功能，让您可以轻松地将语音合成功能集成到您的应用程序中。

先决条件

  • Python 3.10 或更高版本

  • uv包管理器

Related MCP server: Typecast API MCP Server

安装

  1. 首先，安装uv包管理器：

curl -LsSf https://astral.sh/uv/install.sh | sh

  1. 克隆此存储库并安装依赖项：

uv venv
source .venv/bin/activate  # On Windows, use: .venv\Scripts\activate
uv pip install .

特征

  • 具有可定制声音的文本转语音合成

  • 可调节语速

  • 支持将音频保存到文件或直接播放

  • 跨平台音频播放支持（Windows、macOS、Linux）

用法

服务器提供了一个单独的MCP工具generate_speech ，其参数如下：

  • text （必需）：要转换为语音的文本

  • voice （可选）：用于合成的语音（默认值：“af_heart”）

  • speed （可选）：语速倍数（默认值：1.0）

  • save_path （可选）：保存音频文件的目录

  • play_audio （可选）：是否立即播放音频（默认值：False）

示例用法

from mcp.client import Client

async with Client() as client:
    await client.connect("kokoro-tts")
    
    # Generate and play speech
    result = await client.call_tool(
        "generate_speech",
        {
            "text": "Hello, world!",
            "voice": "af_heart",
            "speed": 1.0,
            "play_audio": True
        }
    )

依赖项

  • kokoro >= 0.8.4

  • mcp[cli] >= 1.3.0

  • 声音文件 >= 0.13.1

平台支持

支持音频播放：

  • Windows（使用start ）

  • macOS（使用afplay ）

  • Linux（使用aplay ）

MCP 配置

将以下配置添加到您的 MCP 设置文件：

{
  "mcpServers": {
    "kokoro-tts": {
      "command": "/Users/giannisan/pinokio/bin/miniconda/bin/uv",
      "args": [
        "--directory",
        "/Users/giannisan/Documents/Cline/MCP/kokoro-tts-mcp",
        "run",
        "tts-mcp.py"
      ]
    }
  }
}

执照

[在此添加您的许可证信息]

Available Tools

1 tool
generate_speechD
ParametersJSON Schema
NameRequiredDescriptionDefault
textYes
voiceNoaf_heart
speedNo
save_pathNo
play_audioNo

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 updatev0.2.0
    • First observedgenerate_speech
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion. The tool's purpose is clearly distinct.

Naming Consistency5/5

The single tool name 'generate_speech' follows a clear verb_noun pattern, which is consistent and descriptive.

Tool Count3/5

One tool for a TTS server is borderline; while it may suffice for basic functionality, it feels thin for a typical service that might include voice selection or other parameters.

Completeness2/5

A single tool for TTS lacks coverage for common operations like listing voices, configuring parameters, or stopping generation, leading to significant gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches