> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rivet

> Give the Sazabi agent tools to inspect actors, call actions, open the Actor Inspector, and manage compute pools in Rivet.

[All Rivet integration capabilities](https://docs.sazabi.com/catalogs/integrations/rivet)

## About

This is an MCP connector that gives the Sazabi agent tools from Rivet's hosted MCP server. Rivet authenticates via OAuth with dynamic client registration — you authorize once in the browser and Sazabi refreshes the token thereafter. Access can be scoped globally to your account or constrained to a specific organization, project, or namespace via the server URL.

**What the agent can do:**

* List and inspect running actors, actor lifecycles, and statuses
* Execute actor actions and query actor history
* Inspect actor state, connections, queues, workflows, and database tables
* Manage Rivet compute pools and runners
* Monitor compute metrics and server performance

## Prerequisites

* An active Rivet account
* Access to the Rivet organization, project, or namespace you want to connect

## Set up in the dashboard

Configure connectors in the dashboard under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find Rivet in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Configure access (optional)

By default, the connector connects to `https://mcp.rivet.dev/mcp`. To constrain access to a specific organization, project, or namespace, append query parameters to the Server URL (for example `https://mcp.rivet.dev/mcp?organization=ORG&project=PROJECT&namespace=NS`).

**Step 3**

### Authorize

Start the connection; Sazabi redirects you to Rivet to authorize, then back.

## Set up with the CLI

You can also connect Rivet with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)).

Rivet authenticates over OAuth, so the CLI opens a browser to complete authorization:

```bash theme={"system"}
sazabi mcp-connectors connect rivet
```

Add `--read-only` to restrict the connector to read-only tools, or `--project-id <project>` to target a specific project. In `--json` mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with `sazabi mcp-connectors list`.

## Verify

Open the connector's connection page under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to list running actors or check an actor's status to confirm it runs.

## Troubleshooting

**No tools discovered** — Disconnect and reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) to restart the OAuth flow.

**Connection shows needs attention** — The authorization may have expired or been revoked; reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.

> [card] [Rivet MCP documentation](https://rivet.dev/docs/mcp)
>
> Official Rivet MCP setup and usage guide.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.