Speech.sh vs MCP Fish

In-depth architectural comparison of the Speech.sh and MCP Fish 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.

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 MCP Fish 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).
• Primary tools included: fish_generate_audio, fish_list_models, fish_get_model.

Feature & Specification Comparison

Specification	Speech.sh j3k0 Text-to-Speech	MCP Fish Text-to-Speech
Summary	Let the agent speak things out loud, notify you when he's done working with a quick summary	MCP server exposing the AceDataCloud Fish Audio API (text-to-speech with voice conditioning)
Category & Scope	Text-to-Speech	Text-to-Speech

Tools & Capabilities Breakdown

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).

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

{
  "mcpServers": {
    "mcp-fish": {
      "command": "uvx",
      "args": [
        "mcp-fish"
      ]
    }
  }
}

Related MCP Server Comparisons