Ext Ops Panel
Open dashboard
Comparison

Obsidian vs pmm

Obsidian is an MCP server published by MarkusPfundstein. Marketplaces we read that list it: 1 (Docker MCP Catalog). pmm is a plugin bundle for AI coding tools published by NominexHQ. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
MarketplaceObsidianpmm
Docker MCP Catalog Listed
Version: sha256:0eba4c05742a
Forks (GitHub): 505
Pulls (Docker Hub): 141 997
Stars (Docker Hub): 31
Stars (GitHub): 4 473
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 2.7.0
Forks (GitHub): 8
Stars (GitHub): 15
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 pmm
FactObsidianpmm
Marketplaces that list it11
Stars (GitHub) (differs)4 473 (better)15 (worse)
Pulls (Docker Hub) (differs)141 997No figure on Docker Hub
Forks (GitHub) (differs)505 (better)8 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/obsidian)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle14
LicenceMITMIT
Repository (differs)github.com/markuspfundstein/mcp-obsidiangithub.com/nominexhq/pmm-plugin
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.

pmm

In its own words, on Claude Code: claude-plugins-community:

If you have ever had AI hallucinate and make things up (and gaslight you, even): it's because summaries do not preserve nuance. Each /compact cycle summarises and compresses. Decisions lose their rationale. Lessons lose their context. By Monday, you're re-explaining choices you made on Thursday. That's context rot. PMM fixes that. Every session, Claude loads what it already knows, then adds to it. Markdown files, git-backed. No database, no setup. Decisions tracked with rationale: not just what but. git log as your memory audit trail. Memory that compounds, not rots.

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)

pmm As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install pmm@claude-community

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

Tools each declares

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

Settings each asks for

The marketplaces of pmm publish no settings it asks for, so we do not compare settings.

What it can do: Obsidian · What it can do: pmm · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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