Whisper MCP vs Server Everything
A side-by-side look at the Whisper MCP and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Whisper MCP for speech-to-text work as a local process; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Whisper MCP when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a local stdio subprocess transport.
- You want tools like
transcribe_audio, list_whisper_models, download_whisper_model.
Choose Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Speech-to-Text | Other Tools and Integrations |
| Quality signal | 63/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 91,486 |
| Directory activity | 4 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Whisper MCP | View Server Everything |
Tools & capabilities
Whisper MCP tools 3
transcribe_audioTranscribe an audio file using Whisper. Supports various audio formats (wav, mp3, m4a, etc.). Returns the transcribed text.list_whisper_modelsList available Whisper models and their download status. Shows which models are downloaded locally.download_whisper_modelDownload a Whisper model for local transcription. Models are stored in ~/.whisper/
Server Everything 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.
Whisper MCP
{
"mcpServers": {
"whisper-mcp": {
"command": "npx",
"args": [
"-y",
"whisper-mcp"
]
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
Whisper MCP is categorized under Speech-to-Text and uses a local stdio subprocess. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Whisper MCP for speech-to-text work and Server Everything for other tools and integrations.
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.
Whisper MCP has no declared pricing — check the project's own site. Server Everything is listed as free. Auth: no auth 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 whisper-mcp and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Whisper MCP has a quality signal of 63/100 (Good) with 4 views, 0 installs and 3 GitHub stars. Server Everything has 55/100 (Good) with 9 views, 0 installs and 91,486 GitHub stars.