From 9929fb0d45da9ccb1234316f5ca7b69332cf113e Mon Sep 17 00:00:00 2001 From: Nicholas Kissel Date: Wed, 9 Sep 2026 21:26:10 +0000 Subject: [PATCH 1/5] docs(website): launch Rivet MCP Amp-Thread-ID: https://ampcode.com/threads/T-01a08801-a02c-730d-a83e-93b62350266f Co-authored-by: Nicholas Kissel --- .../2026-09-10-introducing-rivet-mcp/page.mdx | 102 ++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx diff --git a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx new file mode 100644 index 00000000..c97e79d8 --- /dev/null +++ b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx @@ -0,0 +1,102 @@ +--- +author: nathan-flurry +published: "2026-09-10" +category: changelog +keywords: ["mcp", "model context protocol", "ai clients", "claude code", "codex", "cursor", "gemini cli", "vs code", "actor inspector", "rivet actors"] +title: "Introducing Rivet MCP: Connect Your AI Client to Rivet Actors" +seoTitle: "Rivet MCP: Connect Your AI Client to Rivet Actors" +description: "Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code to Rivet to list actors, call actions, and open the Actor Inspector inline from one hosted MCP endpoint." +--- + +Rivet MCP is now available at `https://mcp.rivet.dev/mcp`. Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code and ask about your actors in plain language: which ones are awake, what an action returns, or open the Actor Inspector inside the conversation. + +## Connect Your Client + +Add the endpoint, then approve the Rivet sign-in when it opens. + + + +```sh Claude Code +claude mcp add --transport http rivet https://mcp.rivet.dev/mcp +``` + +```sh Codex +codex mcp add rivet --url https://mcp.rivet.dev/mcp +``` + +```json Cursor +{ + "mcpServers": { + "rivet": { + "url": "https://mcp.rivet.dev/mcp" + } + } +} +``` + +```sh Gemini CLI +gemini mcp add --transport http rivet https://mcp.rivet.dev/mcp +``` + +```sh VS Code +code --add-mcp '{"name":"rivet","type":"http","url":"https://mcp.rivet.dev/mcp"}' +``` + + + +## Find Running Actors + +```text Prompt +Which chat rooms are still awake? +``` + +Rivet MCP finds `rivet.actors.list`, lists the `chat-room` actors, and answers: **3 rooms awake**. + +## Call an Actor Action + +```text Prompt +What has Acme been saying? +``` + +Rivet MCP calls the `getHistory` action on `chat-room · acme` and answers: **128 messages from Acme**. + +## Open the Actor Inspector Inline + +```text Prompt +Open the Actor Inspector for chat-room · acme. +``` + +The same actor view from the dashboard opens inside the conversation, with **State**, **Connections**, **Queue**, **Workflow**, and **Database** tabs. Clients that cannot render it receive the same details as text. + +## One Request, Two Tools + +Rivet MCP is built around two tools instead of a long list of narrow ones. `search` returns the operations that apply to your namespace. `execute` runs one composed JavaScript request and returns one answer. + +```js +// "Which chat rooms are still awake, and what has Acme been saying?" +const { actors } = await rivet.actors.list({ filters: { name: "chat-room" } }); +const awake = actors.filter((room) => room.status === "running"); + +const history = await rivet.actor.action({ + actor: { name: "chat-room", key: ["acme"], method: "get" }, + name: "getHistory", +}); + +return { awake: awake.length, history: history.body.output }; +``` + +## Scope Access + +Pin a connection to one organization, project, or namespace with the slugs from your [dashboard](https://dashboard.rivet.dev) URL. + +```text +https://mcp.rivet.dev/mcp?organization=ORG&project=PROJECT&namespace=NS +``` + +Generated code has no network, filesystem, or environment access. Every call goes through Rivet, which checks it against the access you granted and attaches your credentials, so they never reach the model. + +## More Links + +- [Rivet MCP documentation](/docs/mcp/) +- [GitHub](https://github.com/rivet-dev/rivet) +- [Discord](https://rivet.dev/discord) From 9b3f2677538bd826c6be65fd24ed250a336fd4cb Mon Sep 17 00:00:00 2001 From: Nicholas Kissel Date: Thu, 10 Sep 2026 05:48:14 +0000 Subject: [PATCH 2/5] docs(website): simplify Rivet MCP launch post Amp-Thread-ID: https://ampcode.com/threads/T-01a08801-a02c-730d-a83e-93b62350266f Co-authored-by: Nicholas Kissel --- .../2026-09-10-introducing-rivet-mcp/page.mdx | 62 +++---------------- 1 file changed, 8 insertions(+), 54 deletions(-) diff --git a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx index c97e79d8..40e91c96 100644 --- a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx +++ b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx @@ -3,17 +3,14 @@ author: nathan-flurry published: "2026-09-10" category: changelog keywords: ["mcp", "model context protocol", "ai clients", "claude code", "codex", "cursor", "gemini cli", "vs code", "actor inspector", "rivet actors"] -title: "Introducing Rivet MCP: Connect Your AI Client to Rivet Actors" -seoTitle: "Rivet MCP: Connect Your AI Client to Rivet Actors" -description: "Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code to Rivet to list actors, call actions, and open the Actor Inspector inline from one hosted MCP endpoint." +title: "Introducing Rivet MCP" +description: "Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code to Rivet to list actors, call actions, and open the Actor Inspector from your AI client." --- -Rivet MCP is now available at `https://mcp.rivet.dev/mcp`. Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code and ask about your actors in plain language: which ones are awake, what an action returns, or open the Actor Inspector inside the conversation. +Rivet MCP lets your AI client work with your Rivet Actors. Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code to `https://mcp.rivet.dev/mcp`, approve the Rivet sign-in, and ask about your actors in plain language. ## Connect Your Client -Add the endpoint, then approve the Rivet sign-in when it opens. - ```sh Claude Code @@ -44,56 +41,13 @@ code --add-mcp '{"name":"rivet","type":"http","url":"https://mcp.rivet.dev/mcp"} -## Find Running Actors - -```text Prompt -Which chat rooms are still awake? -``` - -Rivet MCP finds `rivet.actors.list`, lists the `chat-room` actors, and answers: **3 rooms awake**. - -## Call an Actor Action - -```text Prompt -What has Acme been saying? -``` - -Rivet MCP calls the `getHistory` action on `chat-room · acme` and answers: **128 messages from Acme**. - -## Open the Actor Inspector Inline - -```text Prompt -Open the Actor Inspector for chat-room · acme. -``` +## What You Can Ask -The same actor view from the dashboard opens inside the conversation, with **State**, **Connections**, **Queue**, **Workflow**, and **Database** tabs. Clients that cannot render it receive the same details as text. - -## One Request, Two Tools - -Rivet MCP is built around two tools instead of a long list of narrow ones. `search` returns the operations that apply to your namespace. `execute` runs one composed JavaScript request and returns one answer. - -```js -// "Which chat rooms are still awake, and what has Acme been saying?" -const { actors } = await rivet.actors.list({ filters: { name: "chat-room" } }); -const awake = actors.filter((room) => room.status === "running"); - -const history = await rivet.actor.action({ - actor: { name: "chat-room", key: ["acme"], method: "get" }, - name: "getHistory", -}); - -return { awake: awake.length, history: history.body.output }; -``` - -## Scope Access - -Pin a connection to one organization, project, or namespace with the slugs from your [dashboard](https://dashboard.rivet.dev) URL. - -```text -https://mcp.rivet.dev/mcp?organization=ORG&project=PROJECT&namespace=NS -``` +- **Find actors**: "Which chat rooms are still awake?" +- **Call actions**: "What has Acme been saying?" +- **Inspect actors**: "Open the Actor Inspector for chat-room · acme." The dashboard's actor view opens inside the conversation, with State, Connections, Queue, Workflow, and Database tabs. -Generated code has no network, filesystem, or environment access. Every call goes through Rivet, which checks it against the access you granted and attaches your credentials, so they never reach the model. +Every call goes through Rivet with the access you approved at sign-in. Your credentials never reach the model. To limit a connection to one organization, project, or namespace, add `?organization=ORG&project=PROJECT&namespace=NS` to the endpoint. ## More Links From faa7ce48621635a7a0b48c629e4660e09c2c2650 Mon Sep 17 00:00:00 2001 From: Nicholas Kissel Date: Thu, 10 Sep 2026 05:58:04 +0000 Subject: [PATCH 3/5] docs(website): list clients instead of setup code Amp-Thread-ID: https://ampcode.com/threads/T-01a08801-a02c-730d-a83e-93b62350266f Co-authored-by: Nicholas Kissel --- .../2026-09-10-introducing-rivet-mcp/page.mdx | 36 ++++--------------- 1 file changed, 7 insertions(+), 29 deletions(-) diff --git a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx index 40e91c96..8216e6f8 100644 --- a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx +++ b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx @@ -9,37 +9,15 @@ description: "Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code to Rive Rivet MCP lets your AI client work with your Rivet Actors. Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code to `https://mcp.rivet.dev/mcp`, approve the Rivet sign-in, and ask about your actors in plain language. -## Connect Your Client +## Supported Clients - +- Claude Code +- Codex +- Cursor +- Gemini CLI +- VS Code -```sh Claude Code -claude mcp add --transport http rivet https://mcp.rivet.dev/mcp -``` - -```sh Codex -codex mcp add rivet --url https://mcp.rivet.dev/mcp -``` - -```json Cursor -{ - "mcpServers": { - "rivet": { - "url": "https://mcp.rivet.dev/mcp" - } - } -} -``` - -```sh Gemini CLI -gemini mcp add --transport http rivet https://mcp.rivet.dev/mcp -``` - -```sh VS Code -code --add-mcp '{"name":"rivet","type":"http","url":"https://mcp.rivet.dev/mcp"}' -``` - - +Setup steps for each client are in the [Rivet MCP documentation](/docs/mcp/). ## What You Can Ask From 9cc09770f639f4913869372baf1cd6438f557804 Mon Sep 17 00:00:00 2001 From: Nicholas Kissel Date: Thu, 10 Sep 2026 06:31:23 +0000 Subject: [PATCH 4/5] docs(website): add Rivet Compute capabilities to MCP post Amp-Thread-ID: https://ampcode.com/threads/T-01a08801-a02c-730d-a83e-93b62350266f Co-authored-by: Nicholas Kissel --- src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx index 8216e6f8..6e155284 100644 --- a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx +++ b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx @@ -24,6 +24,11 @@ Setup steps for each client are in the [Rivet MCP documentation](/docs/mcp/). - **Find actors**: "Which chat rooms are still awake?" - **Call actions**: "What has Acme been saying?" - **Inspect actors**: "Open the Actor Inspector for chat-room · acme." The dashboard's actor view opens inside the conversation, with State, Connections, Queue, Workflow, and Database tabs. +- **Manage pools**: read and update the [Rivet Compute](/cloud/docs/compute/) deployment that hosts a namespace's actors. +- **Retrieve compute metrics**: check usage for a deployment. +- **List and retrieve images**: see the Docker images available to run. + +## Access Every call goes through Rivet with the access you approved at sign-in. Your credentials never reach the model. To limit a connection to one organization, project, or namespace, add `?organization=ORG&project=PROJECT&namespace=NS` to the endpoint. From e6c3eec5445e6c9e1803ae7cd712baa9d00a84d0 Mon Sep 17 00:00:00 2001 From: Nicholas Kissel Date: Thu, 10 Sep 2026 16:47:06 +0000 Subject: [PATCH 5/5] docs(website): enable Rivet MCP launch hero Amp-Thread-ID: https://ampcode.com/threads/T-01a08801-a02c-730d-a83e-93b62350266f Co-authored-by: Nicholas Kissel --- src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx index 6e155284..6638d3bc 100644 --- a/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx +++ b/src/content/posts/2026-09-10-introducing-rivet-mcp/page.mdx @@ -2,6 +2,7 @@ author: nathan-flurry published: "2026-09-10" category: changelog +image: true keywords: ["mcp", "model context protocol", "ai clients", "claude code", "codex", "cursor", "gemini cli", "vs code", "actor inspector", "rivet actors"] title: "Introducing Rivet MCP" description: "Connect Claude Code, Codex, Cursor, Gemini CLI, or VS Code to Rivet to list actors, call actions, and open the Actor Inspector from your AI client."