riven-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RIVEN_API_KEY | Yes | Your Riven API key (starts with `rvn_`). | |
| RIVEN_API_BASE | No | Override the chat completions API base URL. | https://api.rivenai.io/v1 |
| RIVEN_COMPUTER_BASE | No | Override the Computer (agentic tasks) API base URL. | https://computer.rivenai.io |
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 |
|---|---|
| riven_chatA | Send a single prompt to a Riven chat model and return the completion text. Use for quick, single-turn questions that don't need agentic research. |
| riven_researchA | Create a Riven Computer research task for the given prompt, run it, poll until it completes (or times out), and return a summary of the resulting thread. Use for open-ended research questions that benefit from multi-step agentic work. |
| riven_councilA | Create a Riven Computer council task, which asks multiple models to answer the same prompt and produces a synthesized verdict plus each model's individual answer. Use when you want a cross-checked or debated answer rather than a single model's view. |
| riven_usageA | Return current usage statistics for the authenticated Riven account. |
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 4 tools
Each tool has a clearly distinct purpose: chat for single-turn, council for multi-model debate, research for multi-step agentic work, and usage for account stats. No overlap or confusion.
All tools follow a consistent 'riven_' prefix with a noun that describes the action: chat, council, research, usage. Predictable and clear.
4 tools is well-scoped for an AI assistant server, covering the main interaction modes without being too few or too many.
The tool set covers the primary use cases (single chat, multi-model, research, usage). Missing tools like account management or model listing, but the core workflows are complete.