In-depth architectural comparison of the RiverScript and Spoken MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
RiverScript
Speech-to-Text · Remote HTTP/SSE
Quality: 30/100 (Emerging) | Auth: No auth required
Spoken
Speech-to-Text · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose RiverScript if you need specialized Speech-to-Text tools running via a hosted cloud SSE transport. Choose Spoken if your workspace requires Speech-to-Text integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
R
Choose RiverScript when:
You need dedicated capabilities in the Speech-to-Text domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Speech-to-Text domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: SPOKEN_API_KEY.
Primary tools included: Returns transcripts with real speaker names, not generic labels, Outputs clean Markdown with timestamps for easy parsing, Supports search by text query or Spotify/YouTube URL.
MCP server for RiverScript, an AI transcription platform - fetches transcripts shared via a link.
Fetch published podcast transcripts as clean Markdown with real speaker names (not "Speaker 1") via the Spoken API. Search episodes, get transcripts, check credit balance.
RiverScript is categorized under Speech-to-Text and uses a remote streaming HTTP/SSE transport. In contrast, Spoken belongs to Speech-to-Text using local stdio subprocess. Select RiverScript when you need capabilities focused on speech-to-text and Spoken when you require tools for speech-to-text.