RiverScript vs MCP Transcribe
A side-by-side look at the RiverScript and MCP Transcribe 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 MCP Transcribe for speech-to-text. 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 MCP Transcribe when
- You need dedicated capabilities in the Speech-to-Text domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
MCP_INTEGRATION_URL.
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 | 41/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | MCP_INTEGRATION_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 8 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View RiverScript | View MCP Transcribe |
Tools & capabilities
RiverScript tools
No tool names declared yet. Check the project README from the listing page.
MCP Transcribe 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.
RiverScript
No confirmed install command for RiverScript yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Transcribe
No confirmed install command for MCP Transcribe yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
RiverScript is categorized under Speech-to-Text and uses an install path we have not confirmed yet. MCP Transcribe belongs to Speech-to-Text and uses an install path we have not confirmed yet. Pick RiverScript for speech-to-text work and MCP Transcribe for speech-to-text.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
RiverScript has no declared pricing — check the project's own site. MCP Transcribe is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 riverscript and transcribe-app-mcp-transcribe 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. MCP Transcribe has 41/100 (Fair) with 3 views, 0 installs and 8 GitHub stars.