PostHog MCP vs ClickHouse
PostHog MCP 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-16. 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 |  ClickHouse | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.1 Forks (GitHub): 1 133 Stars (GitHub): 11 569 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): 208 Stars (GitHub): 887 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:51bcd33e17ad Forks (GitHub): 208 Pulls (Docker Hub): 355 280 Stars (Docker Hub): 3 Stars (GitHub): 887 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 | PostHog MCP | ClickHouse |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 11 569 (better) | 887 (worse) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 355 280 |
| Forks (GitHub) (differs) | 1 133 (better) | 208 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.posthog.com/mcp) | On your machine (mcp-clickhouse) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 3 |
| Environment variables it asks for (differs) | Not published | 16, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/cursor/plugins | github.com/clickhouse/mcp-clickhouse |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 44 h ago, requires a key | no 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
PostHog MCP
Work with PostHog from chat: query product analytics and run SQL, manage feature flags and experiments, triage error tracking issues, and review session replays, surveys, and dashboards (URL-only connector to PostHog's hosted MCP server).
ClickHouse
Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
How to run each
PostHog MCP
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 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-clickhouseRequires: 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.
Only PostHog MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of PostHog MCP publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of PostHog MCP publish no settings it asks for, so we do not compare settings.
What it can do: PostHog MCP · 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.