Your AI assistant reads today’s Rivium docs before it writes your code.

Connect it once to the Rivium MCP server, and it looks up the current SDK version, install line and setup steps instead of answering from memory. It is free and needs no account.

Diagram of a patch bay: a cable runs from the Claude Code jack to the Rivium MCP server jack at https://mcp.rivium.co/mcp, which serves the docs of all eight Rivium cloud services: Push, Trace, Chat, Sync, Flags, A/B Testing, Storage, Auth.

Pick your assistant

Rivium MCP server

https://mcp.rivium.co/mcp

Docs for

  • Push
  • Trace
  • Chat
  • Sync
  • Flags
  • A/B Testing
  • Storage
  • Auth

Connect Claude Code

Run this once in a terminal.

Check it with claude mcp list, or with /mcp inside Claude Code.

Terminal
claude mcp add --transport http rivium https://mcp.rivium.co/mcp

What your assistant gets

Pick a request. The calls and the answers below were recorded from the server, not written for this page.

You ask

  1. Your assistant calls

    get_setup_guide

    {
  "product": "push",
  "platform": "flutter"
}

    Rivium returns

    Set up Rivium Push on Flutter

    Step 1: Install the SDK

    • rivium_push — current version 0.1.23 (from the docs)

    Installation (from “Flutter SDK”)

    Add the dependency to your pubspec.yaml:

    yaml
    dependencies:
  rivium_push: ^0.1.23

    Then fetch the package:

    bash
    flutter pub get

    Cut here: 308 of 6,329 characters shown. Read the Flutter SDK page

  2. Your assistant calls

    read_doc

    {
  "id": "push/sdks-flutter",
  "section": "Quick Start"
}

    Rivium returns

    Page: Flutter SDK (id "push/sdks-flutter", section "Quick Start") URL: https://rivium.co/cloud/rivium-push/docs/sdks-flutter Last updated: 2026-10-12T10:54:06+04:00 Characters 0-330 of 330 (end of page).

    Quick Start

    Initialize RiviumPush before runApp:

    dart
    import 'package:flutter/material.dart';
import 'package:rivium_push/rivium_push.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  await RiviumPush.init(RiviumPushConfig(
    apiKey: 'YOUR_API_KEY_HERE',
  ));

  runApp(const MyApp());
}

    The whole answer. Read the Flutter SDK page

  3. Then it writes the code in your project, from what it just read.

The five tools

All five only read. Your assistant chooses the tool by itself; you do not call them by hand.

Tools of the Rivium MCP server
ToolReturnsExample arguments
list_productsThe Rivium products the server covers, the platforms that have an SDK, and the docs link.{}
search_docsThe best pages for a few words or a short question, each with a short excerpt.{ "query": "upload source maps", "product": "trace" }
read_docOne docs page, or one section of it, as text, with its link and last-updated date.{ "id": "push/sdks-flutter", "section": "Quick Start" }
get_sdk_infoThe SDK package for a product and platform: name, current version, install lines and minimum requirements.{ "product": "push", "platform": "android" }
get_setup_guideThe ordered setup steps for a product and platform: install, keys, initialization, test, common mistakes and links to the full pages.{ "product": "trace", "platform": "nextjs" }

Products covered: Rivium Push, Trace, Chat, Sync, Flags, A/B Testing, Storage and Auth, on Flutter, Android, iOS, React Native, Web, Next.js, Node.js and Laravel wherever the product has an SDK for that platform. The docs page lists the platforms per product.

What it reads, and what it never sees

It reads

  • The public Rivium documentation.
  • Current SDK versions from the public package registries.
  • What your assistant sends it: search words, a page id, a product name and a platform name.

It never sees

  • Your code and your files.
  • Your Rivium project and its settings.
  • Your API keys and server secrets.
  • Your users and their data.

Never paste an API key or a server secret into a chat. The server never needs one.

It needs no account either: there is no login, and nothing links a request to a Rivium account.

The details are in the docs

The server covers all eight Rivium cloud services: Push, Trace, Chat, Sync, Flags, A/B Testing, Storage and Auth. The docs page has example requests for each, what the server logs, and troubleshooting. If your team wants tools that know your project, tell us.

Read the docsContact us