Model Context Protocol
Put Riven inside any MCP client
Riven ships an official Model Context Protocol server. Connect it to Claude Desktop, Cursor, or any MCP-compatible host and Riven's models, research lane, model council and catalog become tools that client can call — over one Riven API key and one bill.
Already have a Riven account? Sign in.
What the Riven MCP server exposes
The server implements the MCP tool surface; your client decides when to call it. Nothing runs outside your client's own confirmation flow.
List workspaces and channels, read channel history, search threads, and post Carson G2-governed updates directly into Riven Comms at rivenai.io/comms by default while staying compatible with external Slack or Microsoft Teams connectors.
Inspect sovereign repositories, merge requests, and CI/CD pipelines at scm.rivenai.io directly from your MCP client without third-party GitHub bridges.
Run single-turn completions, cited Riven Computer research tasks, or multi-model council passes over your Riven Control virtual key.
Query live Riven ERP (0.0.06+e) status and discover the sovereign models, modes, and entitlements bound to your Riven account.
Connect in under five minutes
- 1
Connect via Streamable HTTP (no local install required)
{ "mcpServers": { "riven": { "url": "https://rivenai.io/api/mcp", "headers": { "Authorization": "Bearer rvn_..." } } } }Register https://rivenai.io/api/mcp in any Streamable HTTP MCP host (Riven Relay, Claude, Cursor, or custom connector) to expose Riven Comms, Riven SCM, Riven ERP, and Riven Control immediately.
- 2
Or install the local stdio server
npm install -g @rivenai/mcpFor stdio-only hosts, @rivenai/mcp speaks stdio JSON-RPC and proxies directly to Riven Control and Riven Comms.
- 3
Register stdio config with your local client
{ "mcpServers": { "riven": { "command": "riven-mcp", "env": { "RIVEN_API_KEY": "rvn_..." } } } }Use the same block for Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json) when running over local stdio.
~/Library/Application Support/Claude/claude_desktop_config.json
Add the riven block to mcpServers, then restart Claude Desktop. Riven tools show up in the chat tool picker.
.cursor/mcp.json
Drop the same block into the project or global Cursor MCP config and reload Cursor to see the tools in the AI panel.
stdio JSON-RPC
Point any MCP host at riven-mcp with RIVEN_API_KEY in its environment — the server implements the standard tool/resource surface.
How MCP works
The AI application you already use — Claude Desktop, Cursor, or your own agent — that connects to MCP servers.
A small process that publishes tools, resources and prompts. The Riven server publishes Riven's model access.
stdio for a local server, HTTP/SSE for a remote one. The Riven server runs locally over stdio and calls Riven's API.
Keys, permissions and scope
- • Keep
RIVEN_API_KEYin the client's environment, never in a config file you commit. - • Your MCP client shows which tools are available and asks before it calls one.
- • Use a scoped key with budget limits for production agents; rotate it like any other credential.
- • Usage from MCP calls meters through the same Riven bill as chat, API and agent traffic.
Riven MCP server source and setup notes: