Youtube MCP vs Whipscribe MCP
A side-by-side look at the Youtube MCP and Whipscribe MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
Whipscribe MCPSpeech-to-Text · Local subprocess (stdio)Transcribe audio/video files or URLs via the WhipScribe cloud API and fetch the transcript.40FairAuth: not declaredVerdict: choose Youtube MCP for speech-to-text work over a hosted endpoint; choose Whipscribe MCP for speech-to-text as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Youtube MCP when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
CONTAINER_NAME, PORT, MCP_KEY, OPENAI_API_KEY.
WChoose Whipscribe MCP when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Whipscribe MCP | |
|---|---|---|
| Category | Speech-to-Text | Speech-to-Text |
| Quality signal | 47/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CONTAINER_NAMEPORTMCP_KEYOPENAI_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 32 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Youtube MCP | View Whipscribe MCP |
Tools & capabilities
Youtube MCP tools
No tool names declared yet. Check the project README from the listing page.
Whipscribe MCP 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.
Youtube MCP
{
"mcpServers": {
"format37-youtube-mcp": {
"url": "http://localhost:7001/sse"
}
}
}
Whipscribe MCP
{
"mcpServers": {
"whipscribe-mcp": {
"command": "uvx",
"args": [
"whipscribe-mcp"
]
}
}
}
Frequently asked questions
Youtube MCP is categorized under Speech-to-Text and uses a remote HTTP/SSE transport. Whipscribe MCP belongs to Speech-to-Text and uses a local stdio subprocess. Pick Youtube MCP for speech-to-text work and Whipscribe MCP for speech-to-text.
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.
Youtube MCP has no declared pricing — check the project's own site. Whipscribe MCP 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 format37-youtube-mcp and whipscribe-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Youtube MCP has a quality signal of 47/100 (Fair) with 2 views, 0 installs and 32 GitHub stars. Whipscribe MCP has 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.