Risingwave MCP Server
Query RisingWave streaming databases and monitor jobs through natural language.
Data last scanned today · Reviewed today
Overview
RisingWave MCP Server facilitates direct interaction with RisingWave streaming databases, allowing users to query tables, materialized views, and manage complex infrastructure components like sources, sinks, and UDFs. It provides real-time visibility into streaming job performance, including fragment and actor tracking, as well as Hummock storage analytics. The server leverages FastMCP and risingwave-py to establish an efficient bridge between AI interfaces and database instances. It supports deployments via Docker or local source installation, requiring a connection to a running RisingWave instance for operational capabilities.
Our verdict
This server carries a high-risk security score of 29/100, largely because it is community-maintained rather than official and lacks a defined open-source license. Given the absence of editorially reviewed authentication and read-only mode safety, users should exercise significant caution when connecting this tool to production-grade database environments.
- Supports detailed streaming job and storage performance monitoring
- Zero direct dependencies reduce potential supply-chain vulnerabilities
- Offers clear installation paths via Docker or local Python
- Includes extensive management capabilities for sources and UDFs
- High security risk due to missing audit and license
- Last commit was 114 days ago suggesting slower maintenance
- Not maintained by the official RisingWave organization
Tools
| Tool | Description | Risk |
|---|---|---|
| run_select_query | Execute a SELECT query against RisingWave | low |
| table_row_count | Get the row count for a specific table | low |
| get_table_stats | Get comprehensive statistics for a table | low |
| explain_query | Get query execution plan without running it | low |
| explain_analyze | Execute EXPLAIN ANALYZE for detailed runtime statistics | low |
| explain_distsql | Get distributed execution plan for streaming statements | low |
| show_tables | List all tables in the database | low |
| list_databases | List all databases in the cluster | low |
| describe_table | Describe table structure (columns, types) | low |
| describe_materialized_view | Describe materialized view structure | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the environment prerequisites for running the server from source?
You must have Python 3.10 or newer installed on your system.
›Can I connect to a cloud-hosted RisingWave instance?
Yes, you can use a RisingWave Cloud cluster by configuring the connection string or host parameters in your MCP server environment variables.
›How can I configure the server's connection settings?
You can provide a single PostgreSQL-compatible connection string or specify individual parameters such as host, port, user, password, database, and SSL mode.
›Does the server support different transport protocols?
Yes, when running via Docker, you can configure the MCP_TRANSPORT environment variable to use streamable-http, sse, or stdio.
›What is the default port for the HTTP transport mode?
The server listens on port 8000 by default when using HTTP transport, though this can be configured via the MCP_PORT environment variable.
Alternatives
Badge
Maintain this server? Add the live badge to your README.