Ext Ops Panel
Open dashboard
Comparison

Omi vs vault-pkm

Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). vault-pkm is a plugin bundle for AI coding tools published by AdrianV101. 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
MarketplaceOmivault-pkm
Docker MCP Catalog Listed
Version: sha256:674097f43757
Forks (GitHub): 2 602
Pulls (Docker Hub): 33 759
Stars (Docker Hub): 1
Stars (GitHub): 13 700
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 3.10.1
Forks (GitHub): 3
Stars (GitHub): 14
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

Omi vs vault-pkm
FactOmivault-pkm
Marketplaces that list it11
Stars (GitHub) (differs)13 700 (better)14 (worse)
Pulls (Docker Hub) (differs)33 759No figure on Docker Hub
Forks (GitHub) (differs)2 602 (better)3 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/omi)On your machine (obsidian-pkm)
Transport (differs)stdioNot stated
Tools it declares (differs)6Not published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle14
LicenceMITMIT
Repository (differs)github.com/basedhardware/omigithub.com/adrianv101/obsidian-pkm-plugin
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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

Omi

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for Omi interaction and automation. This server provides tools to read, search, and manipulate Memories and Conversations.

vault-pkm

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

Personal knowledge management for Claude Code. Connect to your Obsidian vault with 20 MCP tools, semantic search, wikilink graph traversal, template-based note creation, link health audits, and cross-session activity logging. Includes 3 autonomous agents and hooks for proactive knowledge capture.

How to run each

Omi As a local MCP server: Docker image

Claude Code
claude mcp add --env "OMI_API_KEY=<YOUR_OMI_API_KEY>" --transport stdio omi -- docker run -i --rm -e OMI_API_KEY mcp/omi

Requires: OMI_API_KEY (secret)

vault-pkm As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vault-pkm@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 vault-pkm publish no list of tools, so we do not compare tools.

Settings each asks for

Only Omi asks for

  • OMI_API_KEY (secret)

Only vault-pkm asks for

  • VAULT_PATH

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

What it can do: Omi · What it can do: vault-pkm · 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