Developer · Remote MCP server

Rivet

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

Visit Rivet's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
dev.rivet/mcp
Version
2.3.17
Status
Active
Category
developer
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-09-16
Updated
2026-09-16
Publisher
dev.rivet
Namespace
Namespace verified by the MCP Registry via the domain rivet.dev · how
Website
rivet.dev/docs
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.rivet.dev/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@rivet-dev/mcp2.3.17stdioRIVET_CLOUD_TOKEN (secret)

How to connect Rivet

Rivet is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.rivet.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @rivet-dev/mcp version 2.3.17. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @rivet-dev/mcp@2.3.17. It reads the environment variable RIVET_CLOUD_TOKEN (secret); set it in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rivet-dev/mcp@2.3.17"
      ],
      "env": {
        "RIVET_CLOUD_TOKEN": "<secret>"
      }
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Rigor MCPVerified statistical inference for AI agents: hypothesis tests, sequential testing, power.Local · stdioPyPI: rigor-mcp
RigourQuality gates for AI agents. Lint, test, build checks with memory persistence.Local · stdionpm: @rigour-labs/mcp
RIPE AtlasRIPE Atlas network measurements - ping, traceroute, DNS, TLS, HTTP, NTP, and probes.Local · stdionpm: ripe-atlas-mcp-server
RiskRover MCPDraft risk-based test plans and assess automated test coverage against product risks with RiskRover.Local · stdionpm: riskrover-mcp-server
rlayShared channels where agents from different vendors collaborate over a relayed message log.Remote · HTTPLive check: sign-in requiredrlay.dev
Rlg MCPMCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio.Local · stdioOCI image (Docker): ghcr.io/sebastienrousseau/rlg-mcp:0.0.14
RLM ToolsPersistent Python sandbox for token-efficient codebase exploration in MCP clients.Local · stdioPyPI: rlm-tools
Roamer MCPProject registry, behavioral specs, and engineering threads for AI coding agent workflows.Remote & Local · HTTP, stdioLive check: sign-in requiredroamer-mcp.mathismeadows.com