SQLite (Archived) vs ClickHouse
SQLite (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). ClickHouse is an MCP server published by ClickHouse. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-12. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:efbc05ccace1 Forks (GitHub): 11 780 Pulls (Docker Hub): 72 656 Stars (Docker Hub): 16 Stars (GitHub): 91 180 Not marked · First seen |
Listed Version: sha256:51bcd33e17ad Forks (GitHub): 209 Pulls (Docker Hub): 344 170 Stars (Docker Hub): 3 Stars (GitHub): 886 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.7.0 Forks (GitHub): 209 Stars (GitHub): 886 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
| Fact | SQLite (Archived) | ClickHouse |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 91 180 (better) | 886 (worse) |
| Pulls (Docker Hub) (differs) | 72 656 (worse) | 344 170 (better) |
| Forks (GitHub) (differs) | 11 780 (better) | 209 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/sqlite) | On your machine (mcp-clickhouse) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 6 | 3 |
| Environment variables it asks for (differs) | Not published | 16, secrets among them: 1 |
| Licence (differs) | NOASSERTION | Apache-2.0 |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/clickhouse/mcp-clickhouse |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
SQLite (Archived)
Database interaction and business intelligence capabilities.
ClickHouse
Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
How to run each
SQLite (Archived) As a local MCP server: Docker image
claude mcp add --transport stdio sqlite -- docker run -i --rm mcp/sqlite
ClickHouse As a local MCP server: PyPI package
claude mcp add --env "CLICKHOUSE_HOST=<YOUR_CLICKHOUSE_HOST>" --env "CLICKHOUSE_PASSWORD=<YOUR_CLICKHOUSE_PASSWORD>" --env "CLICKHOUSE_USER=<YOUR_CLICKHOUSE_USER>" --transport stdio mcp-clickhouse -- uvx mcp-clickhouse
Requires: CLICKHOUSE_HOST, CLICKHOUSE_PASSWORD (secret), CLICKHOUSE_USER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only SQLite (Archived) declares
append_insightcreate_tabledescribe_tableread_querywrite_query
Only ClickHouse declares
list_databasesrun_select_query
Both declare
list_tables
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of SQLite (Archived) publish no settings it asks for, so we do not compare settings.
What it can do: SQLite (Archived) · What it can do: ClickHouse · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.