Chroma vs dev.mnemodb/mnemodb
Chroma is an MCP server published by chroma-core. Marketplaces we read that list it: 1 (Docker MCP Catalog). dev.mnemodb/mnemodb is an MCP server published by mnemodb.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  Chroma |  dev.mnemodb/mnemodb |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c050ca8e1d4e Forks (GitHub): 117 Pulls (Docker Hub): 59 494 Stars (Docker Hub): 5 Stars (GitHub): 599 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.21 Downloads/month (npm): 1 449 Downloads/week (npm): 52 Forks (GitHub): 0 Stars (GitHub): 0 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 | dev.mnemodb/mnemodb |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 599 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 59 494 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 117 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/chroma) | On your machine (@mnemodb/mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 1, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/chroma-core/chroma-mcp | github.com/mnemodb/mnemodb |
| Changes in the last 7 days (differs) | 0 | 1 |
| 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.
dev.mnemodb/mnemodb
Persistent agent memory as plain Markdown in your repo - readable, diffable, with provenance.
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)
dev.mnemodb/mnemodb As a local MCP server: npm package
claude mcp add --transport stdio mnemodb -- npx -y @mnemodb/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of dev.mnemodb/mnemodb publish no list of tools, so we do not compare tools.
Settings each asks for
Only Chroma asks for
CHROMA_API_KEY (secret)
Only dev.mnemodb/mnemodb asks for
MNEMO_STORE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Chroma · What it can do: dev.mnemodb/mnemodb · 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.