Ext Ops Panel
Open dashboard
Comparison

Memory (Reference) vs kbdb

Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). kbdb is an MCP server published by diko316. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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

Where each is published
MarketplaceMemory (Reference)kbdb
Docker MCP Catalog Listed
Version: sha256:db0c2db07a44
Forks (GitHub): 11 780
Pulls (Docker Hub): 553 917
Stars (Docker Hub): 26
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
Downloads/month (npm): 519
Downloads/week (npm): 132
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

Memory (Reference) vs kbdb
FactMemory (Reference)kbdb
Marketplaces that list it11
Stars (GitHub) (differs)91 180 (better)0 (worse)
Pulls (Docker Hub) (differs)553 917No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/memory)On your machine (@dikolab/kbdb)
Transportstdiostdio
Tools it declares (differs)9Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/diko316/knowledge-base-db
Changes in the last 7 days00
First seen2026-10-112026-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

Memory (Reference)

In its own words, on Docker MCP Catalog:

Knowledge graph-based persistent memory system.

kbdb

In its own words, on Official MCP Registry:

A searchable second brain for AI agents: ranked keyword and semantic search over your Markdown.

How to run each

Memory (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio memory -- docker run -i --rm mcp/memory

kbdb As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio kbdb -- npx -y @dikolab/kbdb

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of kbdb publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Memory (Reference) · What it can do: kbdb · 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.

Where the data comes from: how the catalog is built