Open source · MIT · Obsidian MCP

Search your entire vault
in milliseconds.

Seekstone is the fastest way to connect Claude to Obsidian — a filesystem-direct Obsidian MCP server, no plugins, no app required. Searches return in single-digit ms — even on a 10,000-note vault — with up to 47,000× smaller payloads, so Claude reads your whole note library without burning its context.

Works with Claude Desktop, Claude Code, Cursor, and any MCP client.

$ npx -y seekstone init
70–250× faster No plugins required Works offline macOS · Linux · Windows
Benchmarked, not claimed

The only Obsidian MCP server
with published numbers.

Measured against 5 other popular servers — 6 servers total — across 1,000 / 5,000 / 10,000-note vaults — public-domain content, fully reproducible, 20 runs each. The harness and the vaults are open source; clone the repo and verify every figure.

47,000× smaller search payloads ~2 KB vs up to 95 MB at 10k notes
6.2ms warm search at 10,000 notes stays flat as your vault grows
250× faster than the slowest and the gap widens with scale
Warm search latency at 10,000 notes lower is better milliseconds
Seekstone fastest in-process index
6.2ms
obsidian-mcp-pro fs subprocess
430ms
obsidian-mcp-server REST API
732ms
obsidian-mcp fs subprocess
811ms
mcpvault fs subprocess
958ms
mcp-obsidian REST API
1550ms
489×
It doesn't cost context — it doesn't fit

One broad search via a REST-proxy server (mcp-obsidian) returns 97.8 million tokens at 10,000 notes — about 489× larger than Claude's entire ~200K-token context window. The result can't even be sent. Seekstone returns the same search in ~570 tokens.

Same vault, different requirements

No plugin. No app.
No context tax.

What each architecture demands of you — and what it costs your model. Same queries, same committed vaults, 20 runs each.

Requirement Seekstone obsidian-mcp-server #1 by downloads REST-proxy servers
Local REST API plugin Not needed Required Required
Obsidian app running Not needed — works with Obsidian closed Required Required
Search payload @ 10k notes 2.0 KB 47 KB up to 95 MB
Warm search latency @ 10k notes 6.2 ms 732 ms (~118× slower) up to 1,550 ms
Structured frontmatter queries Built-in (query_notes) — property/date/size predicates, ~350 B answers JSONLogic via REST Varies

Full methodology and the six-server comparison on the benchmarks page — reproducible from the open-source harness.

See it in action

Ask in plain English.
Answers from your vault.

Claude Desktop on a real vault — one ranked full-text search, one structured query_notes frontmatter query. Tool-call waits are time-lapsed 6×; prompts and answers play in real time.

17 tools · one warm index

Everything Claude needs
to work your vault.

Everything an Obsidian AI assistant needs — read and write, link-graph and periodic notes, the broadest toolset of any Obsidian MCP server. Four capabilities no other tested server even ships.

search

Full-text search returning ranked excerpts (~120 chars, tunable) — not full notes.

query_notes

Structured queries — frontmatter, date & size predicates. Whole-vault answers in ~350 B.

read_note

Read a note by path. Return a single section, block, or line range.

list_notes

List notes, optionally filtered by folder prefix or tag.

list_tags

Every tag in the vault, sorted by usage count or alphabetically.

outline_note

Heading & block structure — cheap navigation before a targeted read.

get_backlinks

Find all notes that link to a given note.

get_links

List all outgoing wikilinks and markdown links from a note.

get_periodic_note

Read any date's daily / weekly / monthly note — Obsidian closed.

Your context is precious.

Most servers return full note content for every hit — megabytes your model has to read. Seekstone returns short ranked excerpts, so a query that cost 872,000 tokens via the REST plugin costs about 740.

Your vault stays yours.

No Obsidian app, no Local REST API plugin, no cloud. Seekstone reads files straight from disk, makes zero network calls, and sends no telemetry. Writes only ever happen when you ask.

Your files, forever.

Plain Markdown on your machine — nothing to lock you in. Frontmatter edits are byte-identical by design: key order, quote style and comments preserved, proven by the test harness.

30 seconds to first search

Pick your way in.

One npm package, one server. Works with Claude Desktop, Claude Code, Cursor, VS Code, Windsurf — any MCP-over-stdio client.

  1. 1Download seekstone.mcpb from GitHub Releases.
  2. 2Open it with Claude Desktop — double-click in Finder.
  3. 3Pick your Obsidian vault when prompted. Done.
Download .mcpb No terminal · no Node.js required
Installs as seekstone Node ≥ 22

Using Windsurf, Cline, or another client? Read the full install guide →

Good to know

Questions, answered.

Yes. Seekstone works when Obsidian is closed — it reads the vault folder directly from disk, so the app never has to be running.
Yes — that's exactly what Seekstone is. It reads the filesystem directly and bypasses the plugin entirely; no plugins are required at all. Skipping the REST round-trip is the source of the up-to-~47,000× payload reduction.
Seekstone — it's filesystem-direct, so there's no plugin and no running Obsidian app, and it's the only Obsidian MCP server with published, reproducible benchmarks: the smallest search payloads (~2 KB at 10,000 notes) and the fastest warm search (6.2 ms) of the six servers tested.
Yes — Seekstone's query_notes tool filters notes by frontmatter key/value predicates (equals, contains, exists, greater/less-than on numbers and ISO dates), plus tag, folder, modified time, and file size. It returns compact rows rather than note content — a full 10,000-note vault scan costs about 350 bytes of context.
Run npx -y seekstone init — it auto-detects your Obsidian vault and configures Claude Desktop for you (use --client code for Claude Code). That's the fastest way to connect Claude to Obsidian: no Local REST API plugin, no running Obsidian app.
Any client that speaks MCP over stdio works — Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Continue, and more. ChatGPT is the exception for now: it connects to MCP servers remotely, and Seekstone is local-only today (a remote transport is on the roadmap).
Yes. Seekstone works offline — your vault is read straight from local disk, with zero network calls and no cloud services involved.
Seekstone only modifies files when you explicitly call a write tool. It makes no network requests, and the vault path is sandboxed — no tool can read or write outside it.
Yes. Seekstone is tested on macOS, Linux, and Windows in CI on every commit.
It is benchmarked against committed vaults of 1,000, 5,000, and 10,000 notes, and search stays in single-digit milliseconds even at 10k. The in-memory index is a few MB and starts in a few seconds.