FreeTTS vs Speech.sh
A side-by-side look at the FreeTTS and Speech.sh MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FreeTTSText-to-Speech · Local subprocess (stdio)Text to speech in 149 languages: MP3 links from any assistant. Free without an account.40FairAuth: not declaredVerdict: choose FreeTTS for text-to-speech work as a local process; choose Speech.sh for text-to-speech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
FChoose FreeTTS when
- You need dedicated capabilities in the Text-to-Speech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FREETTS_API_KEY.
Choose Speech.sh when
- You need dedicated capabilities in the Text-to-Speech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, SPEECH_VOICE, SPEECH_SPEED, SPEECH_MODEL, SPEECH_API_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F FreeTTS | |
|---|---|---|
| Category | Text-to-Speech | Text-to-Speech |
| Quality signal | 40/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Freemium | BYOK (pay the provider) |
| Required env vars | FREETTS_API_KEY | OPENAI_API_KEYSPEECH_VOICESPEECH_SPEEDSPEECH_MODEL |
Tools & capabilities
FreeTTS tools
No tool names declared yet. Check the project README from the listing page.
Speech.sh tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
FreeTTS
{
"mcpServers": {
"freetts": {
"command": "npx",
"args": [
"-y",
"@freetts/mcp"
],
"env": {
"FREETTS_API_KEY": "YOUR_FREETTS_API_KEY_HERE"
}
}
}
}
Speech.sh
{
"mcpServers": {
"j3k0-speech-sh": {
"url": "https://api.groq.com/openai/v1/audio/speech"
}
}
}
Frequently asked questions
FreeTTS is categorized under Text-to-Speech and uses a local stdio subprocess. Speech.sh belongs to Text-to-Speech and uses a remote HTTP/SSE transport. Pick FreeTTS for text-to-speech work and Speech.sh for text-to-speech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
FreeTTS is listed as freemium — a free tier with paid plans. Speech.sh is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add freetts and j3k0-speech-sh as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FreeTTS has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Speech.sh has 39/100 (Fair) with 2 views, 0 installs and 9 GitHub stars.