Chroma vs Local YDB Toolkit
Chroma is an MCP server published by chroma-core. Marketplaces we read that list it: 1 (Docker MCP Catalog). Local YDB Toolkit is a plugin bundle for AI coding tools published by astandrik. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c050ca8e1d4e Forks (GitHub): 117 Pulls (Docker Hub): 59 247 Stars (Docker Hub): 5 Stars (GitHub): 599 Not marked · First seen |
Not listed |
| Community marketplace astandrik/local-ydb-toolkit | Not listed | Listed Version: 0.1.8 Forks (GitHub): 0 Stars (GitHub): 4 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 | Local YDB Toolkit |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 599 (better) | 4 (worse) |
| Pulls (Docker Hub) (differs) | 59 247 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 117 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/chroma) | On your machine (@astandrik/local-ydb-mcp) |
| 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 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/chroma-core/chroma-mcp | github.com/astandrik/local-ydb-toolkit |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
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.
Local YDB Toolkit
Operate Docker-based local YDB deployments with reusable safety guidance and an optional local stdio MCP server.
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)
Local YDB Toolkit As a Codex plugin
codex plugin marketplace add astandrik/local-ydb-toolkitCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Local YDB Toolkit publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Local YDB Toolkit publish no settings it asks for, so we do not compare settings.
What it can do: Chroma · What it can do: Local YDB Toolkit · 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.