RiverScript

What RiverScript MCP server does

The RiverScript MCP server gives an MCP-compatible AI client access to transcripts hosted by RiverScript, an AI transcription platform. Its documented purpose is narrow: retrieve a transcript when the agent has a link to a shared RiverScript transcript.

This fits workflows where transcription has already happened elsewhere and an agent needs to read the resulting text. For example, a client could use the server as the retrieval step in a workflow that summarizes, analyzes, or otherwise processes a transcript after receiving its shared link. Those downstream operations are not described as built-in server features; they would depend on the connected MCP client or other tools.

The available description does not establish whether the server can start transcriptions, upload media, list a user's transcripts, edit transcript content, or manage RiverScript accounts. Treat it as a shared-transcript retrieval interface unless further documentation confirms additional capabilities.

Tools and capabilities

The RiverScript MCP server is described as providing a tool for fetching transcripts shared through a link. The available material does not provide the tool's exact name, input schema, return format, link requirements, or error behavior.

Its supported capability can be summarized as:

• Retrieve a transcript from a shared RiverScript link.
• Expose that retrieval operation through the Model Context Protocol.
• Supply transcript content to an MCP-compatible AI client for subsequent work.

No separate tools for search, transcript creation, audio processing, exporting, authentication, or account administration are documented.

Limitations and notes

The RiverScript MCP server's README is unavailable in the supplied material, so implementation and operational details cannot be verified here. In particular, the available information does not specify installation commands, package names, transport mode, required environment variables, authentication steps, supported client applications, rate limits, or privacy behavior.

Before adopting it in production, verify how shared links are passed to the tool and whether the target transcripts require access credentials. Also confirm how failures are reported when a link is invalid, unavailable, expired, or restricted. These behaviors matter for automated workflows that depend on reliable transcript retrieval.

The RiverScript MCP server should therefore be evaluated as a focused bridge to shared RiverScript transcripts, not as a complete transcription-management API. Use the source project's current documentation to confirm setup and any capabilities added beyond link-based fetching.