RiverScript vs Transcribe MCP
A side-by-side look at the RiverScript and Transcribe MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RiverScriptSpeech-to-TextMCP server for RiverScript, an AI transcription platform - fetches transcripts shared via a link.37FairAuth: not declaredVerdict: choose RiverScript for speech-to-text work; choose Transcribe 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?
RChoose RiverScript when
- You need dedicated capabilities in the Speech-to-Text domain.
Choose Transcribe MCP when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TRANSCRIBE_MCP_WALLET_KEY. - You want tools like
transcribe_url, find_dead_air, shop_info.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R RiverScript | |
|---|---|---|
| Category | Speech-to-Text | Speech-to-Text |
| Quality signal | 37/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | TRANSCRIBE_MCP_WALLET_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View RiverScript | View Transcribe MCP |
Tools & capabilities
RiverScript tools
No tool names declared yet. Check the project README from the listing page.
Transcribe MCP tools 3
transcribe_urla public audio/video URL → text, timings, detected languagefind_dead_airsubtitles or timings → the spans worth cutting, and what you'd saveshop_infoprices, limits and how payment works
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.
RiverScript
No confirmed install command for RiverScript yet — follow the setup steps linked from its listing page rather than a guessed package name.
Transcribe MCP
{
"mcpServers": {
"transcribe-mcp": {
"command": "npx",
"args": [
"-y",
"transcribe-mcp"
],
"env": {
"TRANSCRIBE_MCP_WALLET_KEY": "YOUR_TRANSCRIBE_MCP_WALLET_KEY_HERE"
}
}
}
}
Frequently asked questions
RiverScript is categorized under Speech-to-Text and uses an install path we have not confirmed yet. Transcribe MCP belongs to Speech-to-Text and uses a local stdio subprocess. Pick RiverScript for speech-to-text work and Transcribe 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. RiverScript has no confirmed install command yet — follow its own setup instructions.
RiverScript has no declared pricing — check the project's own site. Transcribe 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 riverscript and transcribe-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, RiverScript has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Transcribe MCP has 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars.