Ext Ops Panel
Open dashboard
Comparison

Cursor SDK vs ClickHouse

Cursor SDK is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). 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-13. 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
MarketplaceCursor SDKClickHouse
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 066
Stars (GitHub): 11 026
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.0
Downloads/month (PyPI): 240 897
Downloads/week (PyPI): 54 389
Forks (GitHub): 209
Stars (GitHub): 886
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:51bcd33e17ad
Forks (GitHub): 209
Pulls (Docker Hub): 346 287
Stars (Docker Hub): 3
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

Cursor SDK vs ClickHouse
FactCursor SDKClickHouse
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)11 026 (better)886 (worse)
Pulls (Docker Hub) (differs)No figure on Docker Hub346 287
Forks (GitHub) (differs)1 066 (better)209 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-clickhouse)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published3
Environment variables it asks for (differs)Not published16, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITApache-2.0
Repository (differs)github.com/cursor/pluginsgithub.com/clickhouse/mcp-clickhouse
Changes in the last 7 days00
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

Cursor SDK

In its own words, on Cursor: cursor/plugins:

Build apps, scripts, and automations with the TypeScript SDK.

ClickHouse

In its own words, on Official MCP Registry:

Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.

How to run each

Cursor SDK

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

ClickHouse As a local MCP server: PyPI package

Claude Code
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

The marketplaces of Cursor SDK publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Cursor SDK publish no settings it asks for, so we do not compare settings.

What it can do: Cursor SDK · What it can do: ClickHouse · Compare two other plugins

Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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