Ext Ops Panel
Open dashboard
Comparison

io.github.afable702/vault-mcp-tools vs io.github.shaqmughal/seekstone

io.github.afable702/vault-mcp-tools is an MCP server published by afable702. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.shaqmughal/seekstone is an MCP server published by shaqmughal. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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
Marketplaceio.github.afable702/vault-mcp-toolsio.github.shaqmughal/seekstone
Official MCP Registry Listed
Version: 1.0.1
No figure published
Not marked · First seen
Listed
Version: 0.22.4
Downloads/month (npm): 3 839
Downloads/week (npm): 546
Forks (GitHub): 3
Stars (GitHub): 34
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.22.4
Downloads/month (npm): 3 839
Downloads/week (npm): 546
Forks (GitHub): 3
Stars (GitHub): 34
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

io.github.afable702/vault-mcp-tools vs io.github.shaqmughal/seekstone
Factio.github.afable702/vault-mcp-toolsio.github.shaqmughal/seekstone
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub34
Forks (GitHub) (differs)No figure on GitHub3
Last release (differs)Not published2026-10-27
Where it runs (differs)On your machine (vault-mcp-tools)On your machine (seekstone)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 21, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)github.com/afable702/obsidian-mcp-servergithub.com/shaqmughal/seekstone
Changes in the last 7 days (differs)05
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

io.github.afable702/vault-mcp-tools

In its own words, on Official MCP Registry:

Complete Obsidian vault MCP server. 35 tools: notes, search, graph, tags, canvas.

io.github.shaqmughal/seekstone

In its own words, on Official MCP Registry:

Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax.

How to run each

io.github.afable702/vault-mcp-tools As a local MCP server: npm package

Claude Code
claude mcp add --env "OBSIDIAN_HTTP_AUTH_TOKEN=<YOUR_OBSIDIAN_HTTP_AUTH_TOKEN>" --env "OBSIDIAN_REST_TOKEN=<YOUR_OBSIDIAN_REST_TOKEN>" --env "OBSIDIAN_VAULT_PATH=<YOUR_OBSIDIAN_VAULT_PATH>" --transport stdio vault-mcp-tools -- npx -y vault-mcp-tools

Requires: OBSIDIAN_HTTP_AUTH_TOKEN (secret), OBSIDIAN_REST_TOKEN (secret), OBSIDIAN_VAULT_PATH

io.github.shaqmughal/seekstone As a local MCP server: npm package

Claude Code
claude mcp add --env "SEEKSTONE_VAULT=<YOUR_SEEKSTONE_VAULT>" --transport stdio seekstone -- npx -y seekstone

Requires: SEEKSTONE_VAULT

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.afable702/vault-mcp-tools asks for

  • OBSIDIAN_HTTP_AUTH_TOKEN (secret)
  • OBSIDIAN_HTTP_PORT
  • OBSIDIAN_REST_PORT
  • OBSIDIAN_REST_TOKEN (secret)
  • OBSIDIAN_TRANSPORT
  • OBSIDIAN_VAULT_PATH

Only io.github.shaqmughal/seekstone asks for

  • SEEKSTONE_VAULT

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

What it can do: io.github.afable702/vault-mcp-tools · What it can do: io.github.shaqmughal/seekstone · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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