Rivet

dev.rivetPublished by rivet.devOfficial publisherv2.3.17Updated Oct 24, 2026

Manage Rivet Cloud namespaces and actors, run Code Mode, and open the Rivet Actor Inspector.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Rivet's MCP server lets an assistant manage Rivet Cloud namespaces and actors, run Code Mode, and open the Actor Inspector.

What you can do
Manage Rivet Cloud namespaces and actors, including creating and working with actors in a project. Run Code Mode to execute code against Rivet. Open the Rivet Actor Inspector to examine actor state. Available as a hosted endpoint or a local npm package over stdio.
When to use it
Useful when you work with Rivet Cloud or a local Rivet engine and want an assistant to handle namespaces, actors and Code Mode runs without switching to the dashboard.
Requirements
Either the remote endpoint at mcp.rivet.dev or the local npm package @rivet-dev/mcp run over stdio with Node.js. OAuth authentication is required. The RIVET_CLOUD_TOKEN API token is needed when targeting Rivet Cloud rather than a local engine.
Before you install
The server requires OAuth and, for Rivet Cloud, a Rivet Cloud API token; keep it secret. It can create and change namespaces and actors and run code through Code Mode, so actions may modify or execute things in your Rivet account. Confirm scope before letting it act on production resources.

Installation

In SourceWeft

  1. Open Rivet in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.rivet%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rivet": {
      "type": "http",
      "url": "https://mcp.rivet.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.3.17LatestSep 17, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Rivet integrations

RIVET / AliEV EV Charging Site Intelligence

Published by GitHub account jgaethle10

A remote MCP endpoint that lets an assistant run a free, source-backed EV charging opportunity screen for a given address.

Streamable HTTPWeb executable
Location & LifestyleNot indexed yetOct 24, 2026