Developer documentation

MCP integration

Connect external Model Context Protocol servers to RivetAI using the same scoped REST API.

MCP-ready REST API

Configure your MCP server with the RivetAI API base URL and a Studio-scoped API key. Each tool invocation uses standard REST routes with Bearer authentication.

Configuration

Create a scoped API key with the permissions your MCP tools need
Set BACKEND_URL to the RivetAI API base URL
Pass RIVETAI_API_KEY (or equivalent) to your MCP server process

env

BACKEND_URL=https://api.rivetai.com
RIVETAI_API_KEY=rivetai_sk_YOUR_KEY

Session audit headers

Send an MCP session header on requests so RivetAI can attribute activity in workspace logs. Filter activity with source=mcp in the workspace activity log.

http

Mcp-Session-Id: your-mcp-session-id
Authorization: Bearer rivetai_sk_YOUR_KEY