Chroma vs io.github.kKEo/memors
Chroma is an MCP server published by chroma-core. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.kKEo/memors is an MCP server published by kKEo. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  io.github.kKEo/memors |
|---|---|---|
| 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 |
| Official MCP Registry | Not listed | Listed Version: 1.6.3 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 | io.github.kKEo/memors |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 599 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 59 247 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 117 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/chroma) | On your machine (https://github.com/kKEo/memors/releases/download/v1.6.3/memors-mcp_1.6.3_linux_amd64.tar.gz) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/chroma-core/chroma-mcp | github.com/kkeo/memors |
| Changes in the last 7 days (differs) | 0 | 4 |
| 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.
io.github.kKEo/memors
Local, explainable knowledge base for AI agents: hybrid search with provenance over SQLite.
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)
io.github.kKEo/memors
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.kKEo/memors publish no list of tools, so we do not compare tools.
Settings each asks for
Only Chroma asks for
CHROMA_API_KEY (secret)
Only io.github.kKEo/memors asks for
MEMORS_HOMEMEMORS_KBMEMORS_MODEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Chroma · What it can do: io.github.kKEo/memors · 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.