MCP Listen vs Whipscribe MCP
A side-by-side look at the MCP Listen 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 MCP Listen for speech-to-text work as a local process; 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 MCP Listen when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_audio_devices, capture_audio, voice_query.
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 | 56/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View MCP Listen | View Whipscribe MCP |
Tools & capabilities
MCP Listen tools 3
list_audio_devicesList available microphone input devicescapture_audioRecord audio from the microphone and save as WAVvoice_queryCapture, transcribe on this machine (whisper.cpp), and query a model through the local Ollama daemon
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.
MCP Listen
{
"mcpServers": {
"mcp-listen": {
"command": "npx",
"args": [
"-y",
"mcp-listen"
]
}
}
}
Whipscribe MCP
{
"mcpServers": {
"whipscribe-mcp": {
"command": "uvx",
"args": [
"whipscribe-mcp"
]
}
}
}
Frequently asked questions
MCP Listen is categorized under Speech-to-Text and uses a local stdio subprocess. Whipscribe MCP belongs to Speech-to-Text and uses a local stdio subprocess. Pick MCP Listen 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.
MCP Listen 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 mcp-listen and whipscribe-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Listen has a quality signal of 56/100 (Good) with 0 views, 0 installs and 10 GitHub stars. Whipscribe MCP has 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.