Chroma vs ChromaDB Remote MCP Server
Chroma is an MCP server published by chroma-core. Marketplaces we read that list it: 1 (Docker MCP Catalog). ChromaDB Remote MCP Server is an MCP server published by meloncafe. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  ChromaDB Remote MCP Server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c050ca8e1d4e Forks (GitHub): 117 Pulls (Docker Hub): 60 122 Stars (Docker Hub): 5 Stars (GitHub): 599 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 Forks (GitHub): 5 Stars (GitHub): 12 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 | ChromaDB Remote MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 599 (better) | 12 (worse) |
| Pulls (Docker Hub) (differs) | 60 122 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 117 (better) | 5 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/chroma) | Remote server (meloncafe.github.io/chromadb-remote-mcp/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/chroma-core/chroma-mcp | github.com/meloncafe/chromadb-remote-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (2 days ago) |
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.
ChromaDB Remote MCP Server
Remote ChromaDB vector database MCP server with streamable HTTP transport
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)
ChromaDB Remote MCP Server As a remote MCP server
claude mcp add --transport http chromadb-remote-mcp https://meloncafe.github.io/chromadb-remote-mcp/mcpRequires: CHROMADB_MCP_URL, MCP_AUTH_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ChromaDB Remote MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of ChromaDB Remote MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
Only Chroma asks for
CHROMA_API_KEY (secret)
Only ChromaDB Remote MCP Server asks for
CHROMADB_MCP_URLMCP_AUTH_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Chroma · What it can do: ChromaDB Remote MCP Server · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.