RisingWave — Claude Code MCP server: features and setup
This MCP server for Claude Code connects an agent to RisingWave for database queries and inspection. It can also track streaming job progress.
no license ★ 19 updated 2026-11-09
claude mcp add --env RISINGWAVE_CONNECTION_STR=<RISINGWAVE_CONNECTION_STR> --env MCP_TRANSPORT=<MCP_TRANSPORT> --transport stdio risingwave -- docker run -i --rm -e RISINGWAVE_CONNECTION_STR -e MCP_TRANSPORT docker.io/risingwavelabs/risingwave-mcp-server:0.1.1What RisingWave does
The server lets an agent query RisingWave, inspect database objects, and manage them. Its tools cover table and materialized view listings, SELECT queries, query plans, and streaming job monitoring.
A running RisingWave instance and the RISINGWAVE_CONNECTION_STR connection string are required. The listed setup runs the server in Docker over STDIO, using the risingwavelabs/risingwave-mcp-server:0.1.1 image. Database permissions set the limits: the server exposes DDL and DML operations, so the configured user determines which ones the agent can perform.
What it helps with
- inspect tables and materialized views
- run a SELECT query against RisingWave
- examine a query execution plan
- track streaming job progress
Example prompts for the agent
- List the tables and materialized views in RisingWave.
- Run a SELECT query to count rows in
orders. - Show the execution plan for this query.
How to install RisingWave
Platform CLI
claude mcp add --env RISINGWAVE_CONNECTION_STR=<RISINGWAVE_CONNECTION_STR> --env MCP_TRANSPORT=<MCP_TRANSPORT> --transport stdio risingwave -- docker run -i --rm -e RISINGWAVE_CONNECTION_STR -e MCP_TRANSPORT docker.io/risingwavelabs/risingwave-mcp-server:0.1.1Replace <…> with your own values
Platform CLI
codex mcp add risingwave --env RISINGWAVE_CONNECTION_STR=<RISINGWAVE_CONNECTION_STR> --env MCP_TRANSPORT=<MCP_TRANSPORT> -- docker run -i --rm -e RISINGWAVE_CONNECTION_STR -e MCP_TRANSPORT docker.io/risingwavelabs/risingwave-mcp-server:0.1.1Replace <…> with your own values
Config file
{
"mcpServers": {
"risingwave": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"RISINGWAVE_CONNECTION_STR",
"-e",
"MCP_TRANSPORT",
"docker.io/risingwavelabs/risingwave-mcp-server:0.1.1"
],
"env": {
"RISINGWAVE_CONNECTION_STR": "<RISINGWAVE_CONNECTION_STR>",
"MCP_TRANSPORT": "<MCP_TRANSPORT>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"risingwave": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"RISINGWAVE_CONNECTION_STR",
"-e",
"MCP_TRANSPORT",
"docker.io/risingwavelabs/risingwave-mcp-server:0.1.1"
],
"env": {
"RISINGWAVE_CONNECTION_STR": "<RISINGWAVE_CONNECTION_STR>",
"MCP_TRANSPORT": "<MCP_TRANSPORT>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e RISINGWAVE_CONNECTION_STR=<RISINGWAVE_CONNECTION_STR> -e MCP_TRANSPORT=<MCP_TRANSPORT> risingwave docker run -i --rm -e RISINGWAVE_CONNECTION_STR -e MCP_TRANSPORT docker.io/risingwavelabs/risingwave-mcp-server:0.1.1Replace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about RisingWave
How do I install RisingWave in Claude Code?
Run `claude mcp add --env RISINGWAVE_CONNECTION_STR=<RISINGWAVE_CONNECTION_STR> --env MCP_TRANSPORT=<MCP_TRANSPORT> --transport stdio risingwave -- docker run -i --rm -e RISINGWAVE_CONNECTION_STR -e MCP_TRANSPORT docker.io/risingwavelabs/risingwave-mcp-server:0.1.1`. This starts the MCP server in Docker using STDIO.
What does RisingWave do?
It gives an agent access to a RisingWave database for queries, schema inspection, and database operations. Other tools inspect query plans and monitor streaming jobs.
What does RisingWave need to run?
It requires a running RisingWave instance and the RISINGWAVE_CONNECTION_STR connection string. The listed installation command also uses Docker; database permissions control which operations the agent can perform.