Ext Ops Panel
Open dashboard
Comparison

infra-postgres vs io.github.devopam/mcpg

infra-postgres is a plugin bundle for AI coding tools published by ClickHouse Inc. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.devopam/mcpg is an MCP server published by devopam. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplaceinfra-postgresio.github.devopam/mcpg
Community marketplace clickhouse/agent-skills Listed
Version: 0.1.0
Forks (GitHub): 38
Stars (GitHub): 550
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.3
Downloads/month (PyPI): 379
Downloads/week (PyPI): 72
Forks (GitHub): 1
Stars (GitHub): 13
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

infra-postgres vs io.github.devopam/mcpg
Factinfra-postgresio.github.devopam/mcpg
Marketplaces that list it11
Stars (GitHub) (differs)550 (better)13 (worse)
Forks (GitHub) (differs)38 (better)1 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleOn your machine (mcpg)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/clickhouse/agent-skillsgithub.com/devopam/mcpg
Changes in the last 7 days (differs)01
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

infra-postgres

In its own words, on Community GitHub marketplaces:

Local and cloud workflows for running Postgres with clickhousectl — local Docker-backed Postgres for development (start, psql client, .env wiring, lifecycle) and managed ClickHouse Cloud Postgres services, beta (authentication, service creation, connections and TLS, runtime config, read replicas, failover, point-in-time restore), with a decision tree routing between them

io.github.devopam/mcpg

In its own words, on Official MCP Registry:

Production-grade PostgreSQL MCP server — 254 tools for query, tuning & ops, read-only by default.

How to run each

infra-postgres As a Claude Code plugin

Claude Code
/plugin marketplace add clickhouse/agent-skills
/plugin install infra-postgres@clickhouse-agent-skills

io.github.devopam/mcpg As a local MCP server: PyPI package

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

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

Neither one's marketplaces publish the settings it asks for.

What it can do: infra-postgres · What it can do: io.github.devopam/mcpg · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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