connector-namespaces vs ClickHouse
connector-namespaces is a plugin bundle for AI coding tools published by Azure. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). 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-15. 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 | ||
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.2.0 Forks (GitHub): 7 Stars (GitHub): 20 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): 887 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:51bcd33e17ad Forks (GitHub): 209 Pulls (Docker Hub): 352 668 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 | connector-namespaces | ClickHouse |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 20 (worse) | 887 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 352 668 |
| Forks (GitHub) (differs) | 7 (worse) | 209 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-clickhouse) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 3 |
| Environment variables it asks for (differs) | Not published | 16, secrets among them: 1 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/azure/connectors | 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
connector-namespaces
Interactive GitHub Copilot canvas for discovering, connecting, and managing hosted MCP servers from an Azure Connector Namespace.
ClickHouse
Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
How to run each
connector-namespaces
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-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 connector-namespaces publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of connector-namespaces publish no settings it asks for, so we do not compare settings.
What it can do: connector-namespaces · What it can do: ClickHouse · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/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.