Ext Ops Panel
Open dashboard
Comparison

Obsidian vs Joplin MCP Server

Obsidian is an MCP server published by MarkusPfundstein. Marketplaces we read that list it: 1 (Docker MCP Catalog). Joplin MCP Server is an MCP server published by alondmnt. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-23. 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
MarketplaceObsidianJoplin MCP Server
Docker MCP Catalog Listed
Version: sha256:0eba4c05742a
Forks (GitHub): 508
Pulls (Docker Hub): 145 145
Stars (Docker Hub): 31
Stars (GitHub): 4 487
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.0
Downloads/month (PyPI): 1 144
Downloads/week (PyPI): 183
Forks (GitHub): 18
Stars (GitHub): 174
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 Joplin MCP Server
FactObsidianJoplin MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)4 487 (better)174 (worse)
Pulls (Docker Hub) (differs)145 145No figure on Docker Hub
Forks (GitHub) (differs)508 (better)18 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/obsidian)On your machine (joplin-mcp)
Transportstdiostdio
Tools it declares (differs)12Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
Parts of the bundle (differs)Not a bundle1
Licence (differs)MITNot stated
Repository (differs)github.com/markuspfundstein/mcp-obsidiangithub.com/alondmnt/joplin-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

Obsidian

In its own words, on Docker MCP Catalog:

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

Joplin MCP Server

In its own words, on Official MCP Registry:

FastMCP server exposing Joplin notes, notebooks, tags, and imports.

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)

Joplin MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "JOPLIN_TOKEN=<YOUR_JOPLIN_TOKEN>" --transport stdio joplin-mcp -- uvx joplin-mcp

Requires: JOPLIN_TOKEN (secret)

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

Tools each declares

The marketplaces of Joplin MCP Server 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 Joplin MCP Server asks for

  • JOPLIN_TOKEN (secret)
  • JOPLIN_URL

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

What it can do: Obsidian · What it can do: Joplin MCP Server · 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