Riverside MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Required for tool calls; without it a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Riverside through Cotlet.dev. Call riverside_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| riverside_guideA | How to work in Riverside (create studios and schedule recordings): its screens and the sign-in link. Call this first. |
| riverside_statusA | Check that your Cotlet.dev account and Riverside are ready: account, credits and Riverside connection. |
| riverside_openA | Open a Riverside page in your signed-in Cloud Browser (default https://riverside.com) to work with create studios and schedule recordings. |
| riverside_readA | Read the current Riverside page: its text and numbered buttons, links and fields. |
| riverside_clickB | Click a numbered element on the current Riverside page. |
| riverside_typeB | Type text into a numbered field on the current Riverside page. |
| riverside_closeA | Close the Riverside browser session when the work is done, so credits stop running. |
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 7 tools
Each tool has a clearly distinct role: open/close manage the browser session, read/click/type operate on the current page, and guide/status cover onboarding versus readiness checks. There is no meaningful overlap between page interaction, session lifecycle, and account checks.
All tools use a consistent riverside_ snake_case prefix, making them easy to group and recognize. The only minor deviation is that guide and status are noun-like names while the other tools use verbs, but the pattern remains predictable.
Seven tools is well-scoped for a browser-automation server: five core browser primitives plus two setup/guidance tools. No tool feels redundant or conspicuously missing from the set.
The surface covers the essential lifecycle: check readiness, open the browser, read the page, click and type, then close the session. It may lack explicit wait/navigation/keyboard primitives, but these are minor gaps for the stated Riverside studio and scheduling workflows.