riverside-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RIVERSIDE_API_KEY | Yes | Your Riverside Business API key | |
| RIVERSIDE_DOWNLOAD_DIR | No | Directory to download files to (default: ./downloads) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspaceA | List productions, studios, and projects in the Riverside workspace. |
| list_recordingsC | List Riverside recordings with optional workspace, date, and page filters. |
| get_recordingA | Get a recording including tracks, files, and transcription details. |
| delete_recordingA | Soft-delete a recording and its associated tracks and files. This is destructive. |
| list_exportsC | List exported Riverside media with optional filters. |
| get_exportB | Get details for a Riverside export. |
| delete_exportA | Permanently delete a Riverside export. This cannot be undone. |
| download_fileC | Download a Riverside track file to the configured local download directory. |
| download_transcriptionC | Download a recording transcription as SRT or TXT. |
| download_exportC | Download an exported video or audio file. |
| create_webinar_registrantC | Register a participant for a Riverside webinar event. |
| get_webinar_registrantsB | List webinar registrants with cursor pagination, filtering, and sorting. |
| list_editsC | List Riverside edits (clips) with optional filters. |
| create_timeline_exportC | Queue an XML or AAF editing-timeline export for an edit. |
| get_timeline_exportA | Get timeline export status. Poll until done or failed. |
| download_timelineC | Download a completed timeline export ZIP. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool targets a distinct resource or action. Download tools are differentiated by target (export, track file, timeline zip, transcription). CRUD operations for recordings, exports, timelines, and webinars are clearly separated.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_timeline_export, delete_recording, list_recordings). There are no mixed conventions or ambiguous verbs.
With 16 tools, the server covers a broad but well-scoped set of operations for managing Riverside media, exports, timelines, webinars, and workspace. Each tool serves a clear purpose and the count feels appropriate for the domain.
The tool surface covers core workflows: CRUD for recordings, exports, and timelines, plus webinar registration and workspace listing. Minor gaps exist (e.g., no update for recordings/exports, no create for edits), but they don't hinder primary use cases.