Chroma vs clickhouse-js-node-troubleshooting
Chroma is an MCP server published by chroma-core. Marketplaces we read that list it: 1 (Docker MCP Catalog). clickhouse-js-node-troubleshooting is a plugin bundle for AI coding tools published by ClickHouse Inc. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-30. 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 |  Chroma |  clickhouse-js-node-troubleshooting |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c050ca8e1d4e Forks (GitHub): 120 Pulls (Docker Hub): 61 605 Stars (Docker Hub): 5 Stars (GitHub): 600 Not marked · First seen |
Not listed |
| Community marketplace clickhouse/agent-skills | Not listed | Listed Version: 0.1.0 Forks (GitHub): 38 Stars (GitHub): 562 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 | Chroma | clickhouse-js-node-troubleshooting |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 600 (better) | 562 (worse) |
| Pulls (Docker Hub) (differs) | 61 605 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 120 (better) | 38 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/chroma) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/chroma-core/chroma-mcp | github.com/clickhouse/agent-skills |
| 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
Chroma
A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma.
clickhouse-js-node-troubleshooting
Troubleshooting guide for the ClickHouse Node.js client (@clickhouse/client) — socket hang-up/ECONNRESET, Keep-Alive, data type mismatches, read-only users, proxy/pathname URLs, TLS, compression, logging, and query parameters
How to run each
Chroma As a local MCP server: Docker image
claude mcp add --env "CHROMA_API_KEY=<YOUR_CHROMA_API_KEY>" --transport stdio chroma -- docker run -i --rm -e CHROMA_API_KEY mcp/chromaRequires: CHROMA_API_KEY (secret)
clickhouse-js-node-troubleshooting As a Claude Code plugin
/plugin marketplace add clickhouse/agent-skills
/plugin install clickhouse-js-node-troubleshooting@clickhouse-agent-skillsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of clickhouse-js-node-troubleshooting publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of clickhouse-js-node-troubleshooting publish no settings it asks for, so we do not compare settings.
What it can do: Chroma · What it can do: clickhouse-js-node-troubleshooting · 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.