Ext Ops Panel
Open dashboard
Comparison

SQLite (Archived) vs postgres-best-practices

SQLite (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-08. 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
MarketplaceSQLite (Archived)postgres-best-practices
Docker MCP Catalog Listed
Version: sha256:efbc05ccace1
Forks (GitHub): 11 931
Pulls (Docker Hub): 77 389
Stars (Docker Hub): 16
Stars (GitHub): 91 873
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

SQLite (Archived) vs postgres-best-practices
FactSQLite (Archived)postgres-best-practices
Marketplaces that list it11
Stars (GitHub) (differs)91 873 (better)3 031 (worse)
Pulls (Docker Hub) (differs)77 389No figure on Docker Hub
Forks (GitHub) (differs)11 931 (better)263 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sqlite)Remote server (mcp.supabase.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/supabase/agent-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-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

SQLite (Archived)

In its own words, on Docker MCP Catalog:

Database interaction and business intelligence capabilities.

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

SQLite (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio sqlite -- docker run -i --rm mcp/sqlite

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

The marketplaces of postgres-best-practices publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: SQLite (Archived) · What it can do: postgres-best-practices · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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