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
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.
Open the connector
Find Rivet in Settings > MCP connectors.
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).
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 (installed and authenticated — see sazabi mcp-connectors reference).
Rivet authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect rivetAdd --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 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 to restart the OAuth flow.
Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.