Skip to main content
Glama
enesjakozh
giannisanni

Kokoro TTS MCP Server

by giannisanni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Kokoro TTS MCP サーバー

Kokoro TTSエンジンを用いたテキスト読み上げ機能を提供するモデルコンテキストプロトコル（MCP）サーバーです。このサーバーは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
        }
    )

依存関係

  • ココロ >= 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