rivet.dev
Rivet provides infrastructure components for durable actors, agent runtimes, workflows, and dynamic app deployment. Its products let developers run stateful backends and AI-agent-related workloads locally or on Rivet Cloud.
Rivet exposes an OAuth-protected hosted MCP server at mcp.rivet.dev, a cloud control-plane HTTP API at api.rivet.dev used by Actors/Dynamic Apps tooling, and an npm-distributed `rivet` CLI for deploy/dev workflows.
- Rivet MCPdetected
- Rivet Cloud control-plane HTTP APIdiscovered
- Rivet CLIdiscovered
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
In the Rivet dashboard, go to Settings > Advanced > Cloud Token in dashboard.rivet.dev and issue a cloud token. Keep it server-side. The Dynamic Apps docs say deployApp() uses RIVET_CLOUD_TOKEN to create each app namespace through the Rivet Cloud API.
Mint a namespace or deployment secret token from the Rivet dashboard, then use it server-side only. Rivet docs show secret tokens with the sk_ prefix and recommend them for private control-plane access and debugging. You can supply it separately as RIVET_TOKEN with RIVET_NAMESPACE, or embed it in the endpoint URL like https://<namespace>:sk_xxxxx@api.rivet.dev. The CLI can also persist credentials after rivet deploy --token <token>.
conventions · 2/8 published
- integrations.json✓https://rivet.dev/.well-known/integrations.json
- llms.txt✓https://rivet.dev/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing