Obsidian Everywhere MCP Server

Graph-native MCP server for reading, navigating, and safely editing Obsidian vaults.

Remote serverstreamable-http

What is the Obsidian Everywhere MCP server?

Graph-native MCP server for reading, navigating, and safely editing Obsidian vaults. That is what the obsidian everywhere mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

  1. Notes are a graph and a semantic knowledge base, not a folder of text files. Backlinks, n-hop neighborhoods, shortest paths, PageRank, full-text search, and local multilingual embeddings turn a topic into focused, token-budgeted context. 2. Your vault should be usable where your agents run. The Remote Vault Bridge exposes that same graph and its guarded write tools over authenticated Streamable HTTP. A Claude Code or Codex process on another server can search, reason over, append to, and reorganize a vault that remains on your own machine.
  • 🧩 Graph + semantic context engine — a markdown parser (wikilinks, embeds,
  • 🌍 Remote Vault Bridge — agents on an external server get the same search,
  • 🧠 Local semantic search — semantic_search and get_related with
  • 🛡️ Safe writes and resilient mounts — partial edits, dry-run-first bulk
  • 🛠️ 39 graph-native MCP tools — structured reads, graph navigation,

The tools it exposes

The server publishes 14 tools. What each one is for:

  • vault_overview — Note counts, top tags, PageRank hub notes, recently modified — a starting orientation
  • vault_status — Mount availability, index freshness, write availability, and last full reconciliation
  • search_notes — Full-text search with tag/folder filters (with a trigram fallback for CJK substring matches unicode61 alone would miss — see DECISIONS.md D9), each
  • semantic_search — Meaning-based search via local embeddings (multilingual-e5-small, no external service) — finds conceptually related notes that don't share the
  • read_note — Structured content/frontmatter/links/tags plus line pagination; optional heading-scoped read
  • list_notes — Explicit folder-aware note listing with pagination; optionally projects named frontmatter fields (e.g. status, project) per note
  • list_folder — Immediate child folders, notes, and attachments
  • regex_search — JavaScript-regex search with file, line, and excerpt
  • get_backlinks — Every note linking to a given note, with the linking sentence
  • get_neighborhood — Explicit n-hop node/edge list around a note (links treated as undirected)
  • get_context_bundleThe killer feature. Center note + prioritized 1-hop neighbors packed into a token budget
  • list_tags — Full nested tag hierarchy with counts

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: OBSIDIAN_EVERYWHERE_CLIENT_TOKEN, OBSIDIAN_VAULT_PATH, OBSIDIAN_EVERYWHERE_TOKEN, OAUTH_LOGIN_SECRET, OAUTH_ISSUER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Obsidian Everywhere's toolset — vault_overview, vault_status, search_notes and 11 more — is a fair guide to whether it matches your workflow. It is maintained by junnnnnw00; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Obsidian Everywhere.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
vault_overviewNote counts, top tags, PageRank hub notes, recently modified — a starting orientation
vault_statusMount availability, index freshness, write availability, and last full reconciliation
search_notesFull-text search with tag/folder filters (with a trigram fallback for CJK substring matches unicode61 alone would miss — see DECISIONS.md D9), each result annotated with link counts and tags
semantic_searchMeaning-based search via local embeddings (multilingual-e5-small, no external service) — finds conceptually related notes that don't share the query's exact words
read_noteStructured content/frontmatter/links/tags plus line pagination; optional heading-scoped read
list_notesExplicit folder-aware note listing with pagination; optionally projects named frontmatter fields (e.g. status, project) per note
list_folderImmediate child folders, notes, and attachments
regex_searchJavaScript-regex search with file, line, and excerpt
get_backlinksEvery note linking to a given note, with the linking sentence
get_neighborhoodExplicit n-hop node/edge list around a note (links treated as undirected)
get_context_bundle**The killer feature.** Center note + prioritized 1-hop neighbors packed into a token budget
list_tagsFull nested tag hierarchy with counts
get_notes_by_tagNotes carrying a given tag (nested-aware)
find_orphansNotes with no incoming or outgoing links

How to install the Obsidian Everywhere MCP server

{
  "mcpServers": {
    "obsidian-everywhere": {
      "command": "npx",
      "args": ["-y", "obsidian-everywhere"],
      "env": {
        "OBSIDIAN_EVERYWHERE_CLIENT_TOKEN": "your-value",
        "OBSIDIAN_VAULT_PATH": "your-value",
        "OBSIDIAN_EVERYWHERE_TOKEN": "your-value",
        "OAUTH_LOGIN_SECRET": "your-value",
        "OAUTH_ISSUER_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
OBSIDIAN_EVERYWHERE_CLIENT_TOKENCredential the server authenticates with.Yes
OBSIDIAN_VAULT_PATHFilesystem location the server is allowed to use.Optional
OBSIDIAN_EVERYWHERE_TOKENCredential the server authenticates with.Yes
OAUTH_LOGIN_SECRETCredential the server authenticates with.Yes
OAUTH_ISSUER_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Obsidian Everywhere to vault overview.
  • Use Obsidian Everywhere to vault status.
  • Use Obsidian Everywhere to search notes.

Frequently asked questions

It connects Obsidian Everywhere to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (vault_overview, vault_status, search_notes, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Obsidian Everywhere directly.