Ext Ops Panel
Open dashboard
Comparison

@henkey/postgres-mcp-server vs postgres-best-practices

@henkey/postgres-mcp-server is an MCP server published by @henkey. Marketplaces we read that list it: 1 (npm registry (MCP servers)). postgres-best-practices is a plugin bundle for AI coding tools published by supabase. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-09. 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
Marketplace@henkey/postgres-mcp-serverpostgres-best-practices
npm registry (MCP servers) Listed
Version: 1.0.7
Downloads/month (npm): 5 607
Downloads/week (npm): 1 856
Forks (GitHub): 37
Stars (GitHub): 204
Not marked · First seen
Not listed
Community marketplace supabase/agent-skills Not listed Listed
Version: not stated
Forks (GitHub): 263
Stars (GitHub): 3 031
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

@henkey/postgres-mcp-server vs postgres-best-practices
Fact@henkey/postgres-mcp-serverpostgres-best-practices
Marketplaces that list it11
Stars (GitHub) (differs)204 (worse)3 031 (better)
Forks (GitHub) (differs)37 (worse)263 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@henkey/postgres-mcp-server)Remote server (mcp.supabase.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)AGPL-3.0Not stated
Repository (differs)github.com/henkdz/postgresql-mcp-servergithub.com/supabase/agent-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-07
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 h ago, requires authentication

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

@henkey/postgres-mcp-server

In its own words, on npm registry (MCP servers):

A Model Context Protocol (MCP) server that provides comprehensive PostgreSQL database management capabilities for AI assistants

postgres-best-practices

In its own words, on Community GitHub marketplaces:

Postgres performance optimization and best practices. Use when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.

How to run each

@henkey/postgres-mcp-server

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

postgres-best-practices As a Claude Code plugin

Claude Code
/plugin marketplace add supabase/agent-skills
/plugin install postgres-best-practices@supabase-agent-skills

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only postgres-best-practices 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

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

What it can do: @henkey/postgres-mcp-server · What it can do: postgres-best-practices · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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