Speech.sh vs Onepin
A side-by-side look at the Speech.sh and Onepin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
OnepinText-to-SpeechAI Voice Production Agent: picks from 30+ TTS models, fixes pronunciation, validates every line.37FairAuth: not declaredVerdict: choose Speech.sh for text-to-speech work over a hosted endpoint; choose Onepin for text-to-speech. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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 | O Onepin | |
|---|---|---|
| Category | Text-to-Speech | Text-to-Speech |
| Quality signal | 39/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | OPENAI_API_KEYSPEECH_VOICESPEECH_SPEEDSPEECH_MODELSPEECH_API_URL |
Tools & capabilities
Speech.sh tools
No tool names declared yet. Check the project README from the listing page.
Onepin 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.
Speech.sh
{
"mcpServers": {
"j3k0-speech-sh": {
"url": "https://api.groq.com/openai/v1/audio/speech"
}
}
}
Onepin
No confirmed install command for Onepin yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Speech.sh is categorized under Text-to-Speech and uses a remote HTTP/SSE transport. Onepin belongs to Text-to-Speech and uses an install path we have not confirmed yet. Pick Speech.sh for text-to-speech work and Onepin 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. Onepin has no confirmed install command yet — follow its own setup instructions.
Speech.sh is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Onepin has no declared pricing — check the project's own site. 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 j3k0-speech-sh and onepin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Speech.sh has a quality signal of 39/100 (Fair) with 2 views, 0 installs and 9 GitHub stars. Onepin has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.