pgops vs RisingWave
pgops is an MCP server published by arzharch. Marketplaces we read that list it: 1 (Official MCP Registry). RisingWave is an MCP server published by risingwavelabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  pgops |  RisingWave |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.9 Downloads/month (PyPI): 239 Downloads/week (PyPI): 21 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.1 Forks (GitHub): 3 Stars (GitHub): 20 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | pgops | RisingWave |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 20 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (pgops-mcp) | On your machine (docker.io/risingwavelabs/risingwave-mcp-server:0.1.1) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 2 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/arzharch/pgops-mcp | github.com/risingwavelabs/risingwave-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-10 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
pgops
Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers
RisingWave
Query, inspect and operate RisingWave, the PostgreSQL-compatible streaming database, from an agent.
How to run each
pgops As a local MCP server: PyPI package
claude mcp add --env "PGOPS_DSN=<YOUR_PGOPS_DSN>" --env "PGOPS_READONLY_DSN=<YOUR_PGOPS_READONLY_DSN>" --transport stdio pgops-mcp -- uvx pgops-mcpRequires: PGOPS_DSN (secret), PGOPS_READONLY_DSN (secret)
RisingWave As a local MCP server: Docker image
claude mcp add --env "RISINGWAVE_CONNECTION_STR=<YOUR_RISINGWAVE_CONNECTION_STR>" --transport stdio risingwave-mcp -- docker run -i --rm -e RISINGWAVE_CONNECTION_STR run -e RISINGWAVE_CONNECTION_STR -e MCP_TRANSPORT=stdio docker.io/risingwavelabs/risingwave-mcp-server:0.1.1 docker.io/risingwavelabs/risingwave-mcp-server:0.1.1Requires: RISINGWAVE_CONNECTION_STR (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only pgops asks for
PGOPS_APPROVAL_MODEPGOPS_AUDIT_LOGPGOPS_DEFAULT_ROW_LIMITPGOPS_DEFAULT_TIMEOUT_MSPGOPS_DSN (secret)PGOPS_MAX_TIMEOUT_MSPGOPS_READONLY_DSN (secret)PGOPS_READ_ONLY
Only RisingWave asks for
MCP_TRANSPORTRISINGWAVE_CONNECTION_STR (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: pgops · What it can do: RisingWave · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.