Ext Ops Panel
Open dashboard
Comparison

pgops vs PostgreSQL performance Tuner MCP Server

pgops is an MCP server published by arzharch. Marketplaces we read that list it: 1 (Official MCP Registry). PostgreSQL performance Tuner MCP Server is an MCP server published by isdaniel. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplacepgopsPostgreSQL performance Tuner MCP Server
Official MCP Registry Listed
Version: 0.1.9
Downloads/month (PyPI): 239
Downloads/week (PyPI): 82
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.5.2
Downloads/month (PyPI): 298
Downloads/week (PyPI): 42
Forks (GitHub): 5
Stars (GitHub): 30
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

pgops vs PostgreSQL performance Tuner MCP Server
FactpgopsPostgreSQL performance Tuner MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)30 (better)
Forks (GitHub) (differs)0 (worse)5 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (pgops-mcp)On your machine (pgtuner-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 2Not published
LicenceNot statedNot stated
Repository (differs)github.com/arzharch/pgops-mcpgithub.com/isdaniel/pgtuner_mcp
Changes in the last 7 days00
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

pgops

In its own words, on Official MCP Registry:

Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers

PostgreSQL performance Tuner MCP Server

In its own words, on Official MCP Registry:

provides AI-powered PostgreSQL performance tuning capabilities.

How to run each

pgops As a local MCP server: PyPI package

Claude Code
claude mcp add --env "PGOPS_DSN=<YOUR_PGOPS_DSN>" --env "PGOPS_READONLY_DSN=<YOUR_PGOPS_READONLY_DSN>" --transport stdio pgops-mcp -- uvx pgops-mcp

Requires: PGOPS_DSN (secret), PGOPS_READONLY_DSN (secret)

PostgreSQL performance Tuner MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio pgtuner-mcp -- uvx pgtuner-mcp

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

The marketplaces of PostgreSQL performance Tuner MCP Server publish no settings it asks for, so we do not compare settings.

What it can do: pgops · What it can do: PostgreSQL performance Tuner MCP Server · 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.

Where the data comes from: how the catalog is built