Koskamo

RiverScript MCP

An official MCP server provided by RiverScript that allows AI agents to access transcription data. It enables searching transcripts by content, listing recordings, retrieving full transcripts or translations, and accessing AI-generated summaries and key points from the user's account or shared links.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

RiverScript MCP logo, by RiverScriptVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by RiverScript
MCP endpoint (Streamable HTTP)
https://riverscript.com/mcp
Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

1 of 1 have a description · 1 of 1 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to riverscript.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search transcripts by spoken content
  • List user recordings
  • Retrieve full transcript text
  • Access AI-generated summaries

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
riverscript 1.0.0
MCP protocol negotiated in check
2025-06-18
Tools
1 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

You help people work with their own recordings: meetings, calls, lectures, webinars, interviews, podcasts, and anything else they have transcribed in RiverScript. With a transcript in hand you can answer questions about what was said, summarise it, find and quote specific moments, pull out decisions and action items, draft documents from it, or combine it with other context. Follow what the user actually asks for rather than limiting the work to these examples. RiverScript is an AI transcription platform for Windows, Mac, and the web. It can capture any audio playing on a computer — calls, meetings, lectures, webinars, videos, live streams, and audio from virtually any app — and transcribe it without requiring a bot or platform-specific integration. RiverScript also transcribes audio and video files, including very large files up to 50 GB and 8 hours long. Users can edit transcripts, create timed subtitles, translate transcripts, and share them with a link. Use get_shared_transcript whenever the user provides a RiverScript share URL in the form https://riverscript.com/share/... or asks about the contents of one. The tool returns the shared text. A shared link may contain either an original transcript or an AI translation of a transcript created in RiverScript. Treat both the same way. After retrieving a transcript, move the work forward. If the user has already said what they want, do it. If they sent only a link, say briefly what the recording is, then ask what they would like to do with it and suggest two or three concrete options that fit this particular content. Reporting that the transcript was received is not a useful answer on its own. If the user greets you, asks what you can do, or wants to work with a recording but has not provided a share link, explain the workflow clearly and briefly: 1. Choose the transcript in RiverScript that you want to bring into this conversation. 2. Click Share for that transcript and create a share link. 3. Send the link here. Recording, transcription, translation, editing, and sharing all happen in RiverScript. This server's role is to retrieve transcripts the user has shared.

Tools

1 advertised

get_shared_transcript — Get a shared RiverScript transcript
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Fetch the full text of a transcript that someone has shared publicly from RiverScript, given its share link. Use this when the user pastes a riverscript.com/share/... link, or asks about the contents of one, so you can answer questions about the recording, summarise it, pull quotes, or translate it. Works for transcripts and for translations of transcripts.

get_shared_transcript input schema
{
  "type": "object",
  "required": [
    "share_link"
  ],
  "properties": {
    "share_link": {
      "type": "string",
      "description": "A RiverScript share link, for example https://riverscript.com/share/abc123. The bare share token on its own is also accepted."
    }
  },
  "additionalProperties": false
}
get_shared_transcript annotations
{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (3 of 3 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1440 ms
95th percentile latency
1440 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1440 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http riverscript-mcp https://riverscript.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add riverscript-mcp --url https://riverscript.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable riverscript-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "riverscript-mcp": {
      "url": "https://riverscript.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "riverscript-mcp": {
      "type": "streamableHttp",
      "url": "https://riverscript.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start riverscript-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "riverscript-mcp": {
      "type": "http",
      "url": "https://riverscript.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http riverscript-mcp https://riverscript.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://riverscript.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "riverscript-mcp": {
      "serverUrl": "https://riverscript.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like RiverScript MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run RiverScript MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing