Ext Ops Panel
Open dashboard
Comparison

PostgreSQL vs PostgreSQL Performance (read-only)

PostgreSQL is an MCP server published by antonorlov. Marketplaces we read that list it: 1 (Official MCP Registry). PostgreSQL Performance (read-only) is an MCP server published by gouranshul. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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

Where each is published
MarketplacePostgreSQLPostgreSQL Performance (read-only)
Official MCP Registry Listed
Version: 0.3.1
Downloads/month (npm): 6 700
Downloads/week (npm): 889
Forks (GitHub): 10
Stars (GitHub): 24
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

PostgreSQL vs PostgreSQL Performance (read-only)
FactPostgreSQLPostgreSQL Performance (read-only)
Marketplaces that list it11
Stars (GitHub) (differs)24 (better)0 (worse)
Forks (GitHub) (differs)10 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp-postgres-server)On your machine (ghcr.io/gouranshul/pg-perf-mcp:0.1.0)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)22, secrets among them: 44, secrets among them: 2
Licence (differs)Not statedMIT
Repository (differs)github.com/antonorlov/mcp-postgres-servergithub.com/gouranshul/pg-perf-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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

PostgreSQL

In its own words, on Official MCP Registry:

MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.

PostgreSQL Performance (read-only)

In its own words, on Official MCP Registry:

Read-only PostgreSQL performance diagnostics: slow queries, EXPLAIN, index advice, locks, functions

How to run each

PostgreSQL As a local MCP server: npm package

Claude Code
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --env "PG_PASSWORD=<YOUR_PG_PASSWORD>" --env "PG_SSH_PASSPHRASE=<YOUR_PG_SSH_PASSPHRASE>" --env "PG_SSH_PASSWORD=<YOUR_PG_SSH_PASSWORD>" --transport stdio mcp-postgres-server -- npx -y mcp-postgres-server

Requires: DATABASE_URL (secret), PG_PASSWORD (secret), PG_SSH_PASSPHRASE (secret), PG_SSH_PASSWORD (secret)

PostgreSQL Performance (read-only)

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: MCP_API_KEY (secret), PGPERF_DB_PASSWORD (secret), PGPERF_DB_URL, PGPERF_DB_USER

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 PostgreSQL asks for

  • DATABASE_URL (secret)
  • PG_ALLOW_WRITE
  • PG_CONNECT_TIMEOUT
  • PG_DATABASE
  • PG_ENABLE_RUNTIME_CONNECT
  • PG_HOST
  • PG_MAX_RESULT_BYTES
  • PG_PASSWORD (secret)
  • PG_PORT
  • PG_SSH_AGENT
  • PG_SSH_FINGERPRINT
  • PG_SSH_HOST
Show the remaining 10
  • PG_SSH_KEEPALIVE_INTERVAL
  • PG_SSH_PASSPHRASE (secret)
  • PG_SSH_PASSWORD (secret)
  • PG_SSH_PORT
  • PG_SSH_PRIVATE_KEY
  • PG_SSH_USER
  • PG_SSLMODE
  • PG_SSL_CA
  • PG_STATEMENT_TIMEOUT
  • PG_USER

Only PostgreSQL Performance (read-only) asks for

  • MCP_API_KEY (secret)
  • PGPERF_DB_PASSWORD (secret)
  • PGPERF_DB_URL
  • PGPERF_DB_USER

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: PostgreSQL · What it can do: PostgreSQL Performance (read-only) · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built