Ext Ops Panel
Open dashboard
Comparison

Obsidian vs Audiobookshelf

Obsidian is an MCP server published by MarkusPfundstein. Marketplaces we read that list it: 1 (Docker MCP Catalog). Audiobookshelf is an MCP server published by ni-c. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceObsidianAudiobookshelf
Docker MCP Catalog Listed
Version: sha256:0eba4c05742a
Forks (GitHub): 508
Pulls (Docker Hub): 145 432
Stars (Docker Hub): 31
Stars (GitHub): 4 487
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (npm): 267
Downloads/week (npm): 33
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

Obsidian vs Audiobookshelf
FactObsidianAudiobookshelf
Marketplaces that list it11
Stars (GitHub) (differs)4 487 (better)1 (worse)
Pulls (Docker Hub) (differs)145 432No figure on Docker Hub
Forks (GitHub) (differs)508 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/obsidian)On your machine (audiobookshelf-mcp)
Transportstdiostdio
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 16, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/markuspfundstein/mcp-obsidiangithub.com/ni-c/audiobookshelf-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.

Audiobookshelf

In its own words, on Official MCP Registry:

Browse your Audiobookshelf libraries and keep listening progress, bookmarks and playlists in sync

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)

Audiobookshelf As a local MCP server: npm package

Claude Code
claude mcp add --env "AUDIOBOOKSHELF_API_KEY=<YOUR_AUDIOBOOKSHELF_API_KEY>" --env "AUDIOBOOKSHELF_URL=<YOUR_AUDIOBOOKSHELF_URL>" --transport stdio audiobookshelf-mcp -- npx -y audiobookshelf-mcp

Requires: AUDIOBOOKSHELF_API_KEY (secret), AUDIOBOOKSHELF_URL

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

Tools each declares

The marketplaces of Audiobookshelf 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 Audiobookshelf asks for

  • AUDIOBOOKSHELF_ALLOW_TOOLS
  • AUDIOBOOKSHELF_API_KEY (secret)
  • AUDIOBOOKSHELF_DENY_TOOLS
  • AUDIOBOOKSHELF_INSECURE_TLS
  • AUDIOBOOKSHELF_READ_ONLY
  • AUDIOBOOKSHELF_URL

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

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