In-depth architectural comparison of the MCP Fish and Speech.sh 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
MCP Fish
Text-to-Speech · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Speech.sh
Text-to-Speech · Remote HTTP/SSE
Quality: 39/100 (Fair) | Auth: API Key required
Verdict Summary: Choose MCP Fish if you need specialized Text-to-Speech tools running via a local process. Choose Speech.sh if your workspace requires Text-to-Speech integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
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).
MCP Fish is categorized under Text-to-Speech and uses a local stdio subprocess. In contrast, Speech.sh belongs to Text-to-Speech using remote streaming HTTP/SSE transport. Select MCP Fish when you need capabilities focused on text-to-speech and Speech.sh when you require tools for text-to-speech.