Whipscribe MCP vs Transkriba — Russian audio transcription
A side-by-side look at the Whipscribe MCP and Transkriba — Russian audio transcription 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 declaredT
Transkriba — Russian audio transcriptionSpeech-to-Text · Remote HTTP/SSETranscribe Russian audio and video with timestamps and optional speaker labels from files or links.38FairAuth: not declaredVerdict: choose Whipscribe MCP for speech-to-text work as a local process; choose Transkriba — Russian audio transcription 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?
WChoose Whipscribe MCP when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a local stdio subprocess transport.
TChoose Transkriba — Russian audio transcription when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Whipscribe MCP | T Transkriba — Russian audio transcription |
|---|---|---|
| Category | Speech-to-Text | Speech-to-Text |
| Quality signal | 40/100 · Fair | 38/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | 1 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Whipscribe MCP | View Transkriba — Russian audio transcription |
Tools & capabilities
Whipscribe MCP tools
No tool names declared yet. Check the project README from the listing page.
Transkriba — Russian audio transcription 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
{
"mcpServers": {
"whipscribe-mcp": {
"command": "uvx",
"args": [
"whipscribe-mcp"
]
}
}
}
Transkriba — Russian audio transcription
{
"mcpServers": {
"transkriba-russian-audio-transcription": {
"url": "https://transkriba.ru/mcp?utm_source=mcp_registry&utm_medium=referral&utm_campaign=remote_server"
}
}
}
Frequently asked questions
Whipscribe MCP is categorized under Speech-to-Text and uses a local stdio subprocess. Transkriba — Russian audio transcription belongs to Speech-to-Text and uses a remote HTTP/SSE transport. Pick Whipscribe MCP for speech-to-text work and Transkriba — Russian audio transcription 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. Transkriba — Russian audio transcription 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 transkriba-russian-audio-transcription 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. Transkriba — Russian audio transcription has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.