Ext Ops Panel
Open dashboard
Comparison

Memory (Reference) vs Obsidian Semantic Search

Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Obsidian Semantic Search is an MCP server published by DalecB. 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

Where each is published
MarketplaceMemory (Reference)Obsidian Semantic Search
Docker MCP Catalog Listed
Version: sha256:db0c2db07a44
Forks (GitHub): 11 790
Pulls (Docker Hub): 556 214
Stars (Docker Hub): 26
Stars (GitHub): 91 268
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Downloads/month (npm): 286
Downloads/week (npm): 66
Forks (GitHub): 0
Stars (GitHub): 1
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 Obsidian Semantic Search
FactMemory (Reference)Obsidian Semantic Search
Marketplaces that list it11
Stars (GitHub) (differs)91 268 (better)1 (worse)
Pulls (Docker Hub) (differs)556 214No figure on Docker Hub
Forks (GitHub) (differs)11 790 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/memory)On your machine (@dalecb/obsidian-semantic-mcp)
Transportstdiostdio
Tools it declares (differs)9Not published
Environment variables it asks for (differs)Not published8, secrets among them: 0
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/dalecb/obsidian-semantic-mcp
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.

Obsidian Semantic Search

In its own words, on Official MCP Registry:

Read-only semantic search MCP server for Obsidian vaults using local Ollama embeddings.

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

Obsidian Semantic Search As a local MCP server: npm package

Claude Code
claude mcp add --env "OBSIDIAN_VAULT_ROOT=<YOUR_OBSIDIAN_VAULT_ROOT>" --transport stdio obsidian-semantic-mcp -- npx -y @dalecb/obsidian-semantic-mcp

Requires: OBSIDIAN_VAULT_ROOT

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

Tools each declares

The marketplaces of Obsidian Semantic Search publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Memory (Reference) publish no settings it asks for, so we do not compare settings.

What it can do: Memory (Reference) · What it can do: Obsidian Semantic Search · 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