# RisingWave

> RisingWave is an open-source MCP server for databases. Query and manage a RisingWave streaming database from an agent over SQL tools. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, self-hosted, API
- **Website:** https://risingwave.com/mcp-streaming-database/
- **Repository:** https://github.com/risingwavelabs/risingwave-mcp
- **MCP Registry name:** io.github.risingwavelabs/risingwave-mcp
- **Categories:** databases
- **Listing updated:** 2026-11-14

## About

RisingWave keeps materialized views up to date as Kafka events and change-data-capture streams arrive, so an agent reading one sees state from seconds ago rather than the last batch load. This server connects to it with a PostgreSQL connection string and registers more than 100 tools built on FastMCP.

The query tool, run_select_query, accepts SELECT and WITH statements only. Schema tools let the agent discover views, sources, sinks and indexes, and bundled documentation tools help it write correct SQL. DDL and DML tools also exist, so the real permission boundary is the database user: the README advises granting SELECT on just a few views, and the site describes a tool allowlist for hosts that should see fewer.

The registry package is a Docker image that speaks stdio; run from source it also defaults to stdio, while the image defaults to streamable HTTP on port 8000 at /mcp. The setup guide covers Claude Desktop, Cursor, VS Code and a Python agent.

## Features

- **Read-only SQL tool:** run_select_query accepts SELECT and WITH statements only.
- **Schema discovery:** List and describe materialized views, sources, sinks and indexes.
- **Bundled docs search:** Search and fetch sections of RisingWave documentation from within the agent.
- **Explain tools:** Plan inspection with explain_query, explain_analyze and explain_distsql.
- **Streaming job monitoring:** README lists fragment, actor and backfill tracking plus storage analysis.
- **Several transports:** stdio, streamable HTTP and SSE are available depending on how it is run.

## Good for

- Let an agent answer questions from live materialized views
- Inspect a streaming pipeline's sources and sinks from chat
- Have an assistant write SQL with help from the bundled docs
- Review query plans for a slow streaming view

## Install

### Claude Code (Terminal)

```sh
claude mcp add risingwave-mcp --env RISINGWAVE_CONNECTION_STR='<RISINGWAVE_CONNECTION_STR>' -- docker run -i --rm -e RISINGWAVE_CONNECTION_STR docker.io/risingwavelabs/risingwave-mcp-server:0.1.1
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "risingwave-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RISINGWAVE_CONNECTION_STR",
        "docker.io/risingwavelabs/risingwave-mcp-server:0.1.1"
      ],
      "env": {
        "RISINGWAVE_CONNECTION_STR": "<RISINGWAVE_CONNECTION_STR>"
      }
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "risingwave-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RISINGWAVE_CONNECTION_STR",
        "docker.io/risingwavelabs/risingwave-mcp-server:0.1.1"
      ],
      "env": {
        "RISINGWAVE_CONNECTION_STR": "<RISINGWAVE_CONNECTION_STR>"
      }
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "risingwave-mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RISINGWAVE_CONNECTION_STR",
        "docker.io/risingwavelabs/risingwave-mcp-server:0.1.1"
      ],
      "env": {
        "RISINGWAVE_CONNECTION_STR": "<RISINGWAVE_CONNECTION_STR>"
      }
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "risingwave-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RISINGWAVE_CONNECTION_STR",
        "docker.io/risingwavelabs/risingwave-mcp-server:0.1.1"
      ],
      "env": {
        "RISINGWAVE_CONNECTION_STR": "<RISINGWAVE_CONNECTION_STR>"
      }
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "risingwave-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RISINGWAVE_CONNECTION_STR",
        "docker.io/risingwavelabs/risingwave-mcp-server:0.1.1"
      ],
      "env": {
        "RISINGWAVE_CONNECTION_STR": "<RISINGWAVE_CONNECTION_STR>"
      }
    }
  }
}
```

## Tools

- `run_select_query`: Run a SELECT or WITH query
- `table_row_count`: Count rows in a table
- `get_table_stats`: Table statistics
- `list_materialized_views`: List materialized views
- `describe_materialized_view`: Describe a materialized view
- `show_create_materialized_view`: Show the definition of a materialized view
- `list_sources`: List sources
- `list_sinks`: List sinks
- `list_indexes`: List indexes
- `search_docs`: Search bundled RisingWave documentation
- `get_doc_section`: Fetch a documentation section
- `list_doc_sections`: List documentation sections
- `explain_query`: Show a query plan
- `explain_analyze`: Run EXPLAIN ANALYZE
- `explain_distsql`: Show a distributed query plan

## FAQ

### How do I limit what the agent can touch?

Connect as a database user with only the privileges needed, such as SELECT on selected views, and use a tool allowlist where the host supports one.

### What does it need to start?

A RISINGWAVE_CONNECTION_STR PostgreSQL connection string; Python 3.10 or newer if run from source.

### Does it only read data?

No. DDL and DML tools exist, so the database user's permissions are what bound it.

### Which hosts are documented?

Claude Desktop, Cursor, VS Code Copilot and a custom Python agent.

### Is RisingWave free?

Yes. RisingWave is open source, so you can use and self-host it for free.

### How do I add RisingWave to Claude Code?

Run this command in your terminal: claude mcp add risingwave-mcp --env RISINGWAVE_CONNECTION_STR='<RISINGWAVE_CONNECTION_STR>' -- docker run -i --rm -e RISINGWAVE_CONNECTION_STR docker.io/risingwavelabs/risingwave-mcp-server:0.1.1

### What are the best alternatives to RisingWave?

The closest alternatives to RisingWave are Midplane, PlatypusDB, Lorebase, Sovaria and model2data studio.

## Alternatives

- [Midplane](https://ai-powered.com/mcp/midplane): Midplane is an open-source MCP server for databases.
- [PlatypusDB](https://ai-powered.com/mcp/platypusdb): PlatypusDB is an open-source MCP server for databases.
- [Lorebase](https://ai-powered.com/mcp/lorebase): Lorebase is an open-source MCP server for knowledge and memory.
- [Sovaria](https://ai-powered.com/mcp/sovaria): Sovaria is a freemium MCP server for databases.
- [model2data studio](https://ai-powered.com/mcp/model2data-studio): model2data studio is a freemium MCP server for databases.
- [semlayer](https://ai-powered.com/mcp/semlayer): semlayer is a free MCP server for databases.
- [bricksentry](https://ai-powered.com/mcp/bricksentry): bricksentry is an open-source MCP server for databases.
- [MCP Toolbox for Databases](https://ai-powered.com/mcp/mcp-toolbox-for-databases-2): MCP Toolbox for Databases is an open-source MCP server for databases.

---
Source: https://ai-powered.com/mcp/risingwave
