What is the key difference between Speech.sh and Kokoro Tts MCP?

Speech.sh belongs to the Text-to-Speech category with cloud HTTP/SSE execution, while Kokoro Tts MCP belongs to the Text-to-Speech category with local stdio execution.

How do I install Speech.sh or Kokoro Tts MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Speech.sh and Kokoro Tts MCP free or paid?

Speech.sh operates under a BYOK (Pay Provider Direct) model (API Key required). Kokoro Tts MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Speech.sh lists 6 tools with 2 views and 9 GitHub stars. Kokoro Tts MCP lists 5 tools with 4 views and 82 GitHub stars.

Can I use both Speech.sh and Kokoro Tts MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Speech.sh vs Kokoro Tts MCP

In-depth architectural comparison of the Speech.sh and Kokoro Tts MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Speech.sh

Text-to-Speech · Remote HTTP/SSE

Quality: 39/100 (Fair) | Auth: API Key required

Kokoro Tts MCP

Text-to-Speech · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Speech.sh if you need specialized Text-to-Speech tools running via a hosted cloud SSE transport. Choose Kokoro Tts MCP if your workspace requires Text-to-Speech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Speech.sh when:

You need dedicated capabilities in the Text-to-Speech domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: OPENAI_API_KEY, SPEECH_VOICE, SPEECH_SPEED, SPEECH_MODEL, SPEECH_API_URL.
Primary tools included: Multiple voice options (troy, austin, hannah, autumn), Adjustable speech speed parameter, Hash-based caching with 24-hour auto-cleanup.

Explore Speech.sh Details

Choose Kokoro Tts MCP when:

You need dedicated capabilities in the Text-to-Speech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_S3_BUCKET_NAME, AWS_S3_REGION, AWS_S3_FOLDER, S3_ENABLED, MP3_FOLDER, TTS_VOICE.

Feature & Specification Comparison

Specification	Speech.sh j3k0 Text-to-Speech	Kokoro Tts MCP mberg Text-to-Speech
Summary	Let the agent speak things out loud, notify you when he's done working with a quick summary	MCP Server that uses the open weight Kokoro TTS models to convert text-to-speech. Can convert text to MP3 on a local driver or auto-upload to an S3 bucket.
Category & Scope	Text-to-Speech

Tools & Capabilities Breakdown

Speech.sh Tools (6)

Multiple voice options (troy, austin, hannah, autumn)

Adjustable speech speed parameter

Hash-based caching with 24-hour auto-cleanup

Retry logic with exponential backoff

Audio playback via ffplay, mplayer, or VLC

MCP server with a single speak tool

Kokoro Tts MCP Tools (5)

Local Kokoro ONNX text-to-speech

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Speech.sh Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "j3k0-speech-sh": {
      "url": "https://api.groq.com/openai/v1/audio/speech"
    }
  }
}

Kokoro Tts MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mberg-kokoro-tts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mberg-kokoro-tts-mcp"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID_HERE",
        "AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY_HERE",
        "AWS_S3_BUCKET_NAME": "YOUR_AWS_S3_BUCKET_NAME_HERE",
        "AWS_S3_REGION": "YOUR_AWS_S3_REGION_HERE",
        "AWS_S3_FOLDER": "YOUR_AWS_S3_FOLDER_HERE",
        "S3_ENABLED": "YOUR_S3_ENABLED_HERE",
        "MP3_FOLDER": "YOUR_MP3_FOLDER_HERE",
        "TTS_VOICE": "YOUR_TTS_VOICE_HERE"
      }
    }
  }
}

Frequently Asked Questions

Speech.sh is categorized under Text-to-Speech and uses a remote streaming HTTP/SSE transport. In contrast, Kokoro Tts MCP belongs to Text-to-Speech using local stdio subprocess. Select Speech.sh when you need capabilities focused on text-to-speech and Kokoro Tts MCP when you require tools for text-to-speech.

More alternatives to Speech.sh More alternatives to Kokoro Tts MCP Text-to-Speech category hub