Ext Ops Panel
Open dashboard
Comparison

Obsidian vs Total Agent Memory

Obsidian is an MCP server published by MarkusPfundstein. Marketplaces we read that list it: 1 (Docker MCP Catalog). Total Agent Memory is an MCP server published by vbcherepanov. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-27. 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
MarketplaceObsidianTotal Agent Memory
Docker MCP Catalog Listed
Version: sha256:0eba4c05742a
Forks (GitHub): 508
Pulls (Docker Hub): 146 645
Stars (Docker Hub): 31
Stars (GitHub): 4 499
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 14.9.0
Downloads/month (PyPI): 1 668
Downloads/week (PyPI): 292
Forks (GitHub): 18
Stars (GitHub): 73
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

Obsidian vs Total Agent Memory
FactObsidianTotal Agent Memory
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)4 499 (better)73 (worse)
Pulls (Docker Hub) (differs)146 645No figure on Docker Hub
Forks (GitHub) (differs)508 (better)18 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (mcp/obsidian)On your machine (total-agent-memory)
Transportstdiostdio
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 12, secrets among them: 0
Hooks it runs (differs)Not published9
Parts of the bundle (differs)Not a bundle12
LicenceMITMIT
Repository (differs)github.com/markuspfundstein/mcp-obsidiangithub.com/vbcherepanov/total-agent-memory
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

Obsidian

In its own words, on Docker MCP Catalog:

MCP server that interacts with Obsidian via the Obsidian rest API community plugin.

Total Agent Memory

In its own words, on Official MCP Registry:

Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall

How to run each

Obsidian As a local MCP server: Docker image

Claude Code
claude mcp add --env "OBSIDIAN_API_KEY=<YOUR_OBSIDIAN_API_KEY>" --transport stdio obsidian -- docker run -i --rm -e OBSIDIAN_API_KEY mcp/obsidian

Requires: OBSIDIAN_API_KEY (secret)

Total Agent Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio total-agent-memory -- uvx total-agent-memory

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

Tools each declares

The marketplaces of Total Agent Memory publish no list of tools, so we do not compare tools.

Settings each asks for

Only Obsidian asks for

  • OBSIDIAN_API_KEY (secret)
  • OBSIDIAN_HOST

Only Total Agent Memory asks for

  • MEMORY_ASYNC_ENRICHMENT
  • MEMORY_MODE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Obsidian · What it can do: Total Agent Memory · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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