A side-by-side look at the Whipscribe MCP and Youtube MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Whipscribe MCP for speech-to-text work as a local process; choose Youtube MCP for speech-to-text over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
W
Choose Whipscribe MCP when
You need dedicated capabilities in the Speech-to-Text domain.
No tool names declared yet. Check the project README from the listing page.
Youtube 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.
Whipscribe MCP is categorized under Speech-to-Text and uses a local stdio subprocess. Youtube MCP belongs to Speech-to-Text and uses a remote HTTP/SSE transport. Pick Whipscribe MCP for speech-to-text work and Youtube 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.
Whipscribe MCP has no declared pricing — check the project's own site. Youtube 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 whipscribe-mcp and format37-youtube-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Whipscribe MCP has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Youtube MCP has 47/100 (Fair) with 2 views, 0 installs and 32 GitHub stars.