Ext Ops Panel
Open dashboard
Comparison

Obsidian vs obsidian-sync

Obsidian is an MCP server published by MarkusPfundstein. Marketplaces we read that list it: 1 (Docker MCP Catalog). obsidian-sync is a plugin bundle for AI coding tools published by chenlei1700. 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
MarketplaceObsidianobsidian-sync
Docker MCP Catalog Listed
Version: sha256:0eba4c05742a
Forks (GitHub): 504
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: 0.1.0
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

Obsidian vs obsidian-sync
FactObsidianobsidian-sync
Marketplaces that list it11
Stars (GitHub) (differs)4 473 (better)0 (worse)
Pulls (Docker Hub) (differs)141 997No figure on Docker Hub
Forks (GitHub) (differs)504 (better)0 (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
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITNot stated
Repository (differs)github.com/markuspfundstein/mcp-obsidiangithub.com/chenlei1700/obsidian-sync
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.

obsidian-sync

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

A Claude Code plugin that syncs project documentation to your Obsidian vault — one command, zero config. The Problem: You clone repos. Each has scattered documentation — .md files, .pdf references — buried in nested directories. You want to read and search them in one place, but they live across dozens of project folders. obsidian-sync moves all project documentation into your Obsidian vault with a single command, keeping them browsable both in Obsidian and in the original project.

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)

obsidian-sync

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 obsidian-sync publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Obsidian · What it can do: obsidian-sync · 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