Skip to content
MCP server

RisingWave

Query and manage a RisingWave streaming database from an agent over SQL tools

Runs locallyStatus and history
Pricing
Open source
Platforms
CLI, self-hosted, API
Runs
Locally
Version
0.1.1
Listing updated
3 days ago

About RisingWave

RisingWave is an open-source MCP server for databases. It runs locally on your machine and is started by your AI client.

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.

Install

Run in a 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

Add to claude_desktop_config.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>"
      }
    }
  }
}

Add to ~/.cursor/mcp.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>"
      }
    }
  }
}

Add to .vscode/mcp.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>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.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>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "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>"
      }
    }
  }
}

Configuration

  • RISINGWAVE_CONNECTION_STRPostgreSQL connection string for RisingWave, e.g. postgresql://user:password@host:4566/dev. Use a user with SELECT on the views the agent may read.Required
  • MCP_TRANSPORTTransport the server speaks. The registry package uses stdio; the image defaults to streamable-http.

Tools this server provides (15)

Taken from the project documentation; the running server may differ.

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

What it does

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

Pricing

Open source

RisingWave is Apache 2.0 self-managed; RisingWave Cloud has a free start and pay-as-you-go plans

Prices change. Check risingwave.com before you buy.

RisingWave 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 to RisingWave

  1. Midplane

    MCP server

    Postgres gateway for AI agents with table grants, column masking and approval for writes

    Runs locally
    • Open source
    • 5 GitHub stars
    • Databases
  2. PlatypusDB

    MCP server

    Gives MCP clients access to your PlatypusDB database connections, scoped per agent

    Runs locally
    • Open source
    • Databases
  3. Lorebase

    MCP server

    Lets agents read and change a governed, versioned Postgres knowledge graph

    Runs locally
    • Open source
    • Knowledge and memory
  4. Sovaria

    MCP server

    Manage a Sovaria backend (Postgres, auth, storage, functions) from an AI assistant

    Not checked yet
    • 4 tools
    • Remote
    • Freemium
    • Databases
  5. Generate realistic connected test data, dbt projects and dashboards from a schema

    • Remote
    • Freemium
    • Databases
  6. semlayer

    MCP server

    Infers a semantic layer from your data warehouse and serves it to agents

    Runs locally
    • Free
    • Databases