Speakvora vs Speech.sh
A side-by-side look at the Speakvora and Speech.sh MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SpeakvoraText-to-SpeechText to speech, voice listing and phrase library search for AI assistants. API key header.37FairAuth: not declaredVerdict: choose Speakvora for text-to-speech work; 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?
SChoose Speakvora when
- You need dedicated capabilities in the Text-to-Speech domain.
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 | S Speakvora | |
|---|---|---|
| Category | Text-to-Speech | Text-to-Speech |
| Quality signal | 37/100 · Fair | 39/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | OPENAI_API_KEYSPEECH_VOICESPEECH_SPEED |
Tools & capabilities
Speakvora 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.
Speakvora
No confirmed install command for Speakvora yet — follow the setup steps linked from its listing page rather than a guessed package name.
Speech.sh
{
"mcpServers": {
"j3k0-speech-sh": {
"url": "https://api.groq.com/openai/v1/audio/speech"
}
}
}
Frequently asked questions
Speakvora is categorized under Text-to-Speech and uses an install path we have not confirmed yet. Speech.sh belongs to Text-to-Speech and uses a remote HTTP/SSE transport. Pick Speakvora 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. Speakvora has no confirmed install command yet — follow its own setup instructions.
Speakvora has no declared pricing — check the project's own site. 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 speakvora and j3k0-speech-sh as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Speakvora has a quality signal of 37/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.