Ext Ops Panel
Open dashboard
Comparison

clickhouse vs PostgreSQL Performance (read-only)

clickhouse is a plugin bundle for AI coding tools published by ClickHouse. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community). 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-19. 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
MarketplaceclickhousePostgreSQL Performance (read-only)
Claude Code: claude-plugins-official Listed
Version: 1.0.0
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 1.0.0
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

clickhouse vs PostgreSQL Performance (read-only)
FactclickhousePostgreSQL Performance (read-only)
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)7 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)2026-10-16Not published
Where it runs (differs)Remote server (mcp.clickhouse.cloud/mcp)On your machine (ghcr.io/gouranshul/pg-perf-mcp:0.1.0)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 2
Parts of the bundle (differs)3Not a bundle
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/clickhouse/clickhouse-claude-code-plugingithub.com/gouranshul/pg-perf-mcp
Changes in the last 7 days (differs)24
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 46 h ago, requires a keyno remote endpoint we check

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

clickhouse

In its own words, on Claude Code: claude-plugins-official:

Connect Claude to your ClickHouse Cloud databases. Browse organizations, services, databases, and table schemas. Run read-only SQL queries against your data and get instant analytical answers. Monitor service backups, review billing costs, and inspect ClickPipe configurations - all through natural conversation.

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

clickhouse As a Claude Code plugin

Claude Code
/plugin install clickhouse@claude-plugins-official

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.

Only clickhouse has a remote endpoint we check. How we check endpoints

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 clickhouse publish no settings it asks for, so we do not compare settings.

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

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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