<p align="center"> <img src="./docs/assets/logo.png" alt="obsidian-mcp-router — multi-vault MCP server" width="540"> </p> <p align="center"> <a href="https://github.com/tboome33/obsidian-mcp-router/actions/workflows/test.yml"><img src="https://github.com/tboome33/obsidian-mcp-router/actions/workflows/test.yml/badge.svg" alt="tests"></a> <a href="./LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-blue.svg" alt="license"></a> <a href="https://nodejs.org"><img src="https://img.shields.io/badge/node-%E2%89%A520.18.1-brightgreen.svg" alt="node"></a> <a href="./CHANGELOG.md"><img src="https://img.shields.io/badge/version-0.64.0-blueviolet.svg" alt="version"></a> </p>

obsidian-mcp-router

🇬🇧 English version below — 🇫🇷 version française

An MCP server that routes Claude tool calls to multiple Obsidian vaults — local or remote — over the Local REST API plugin.

Instead of registering one MCP per vault (one process, one port, one API key), this router exposes a single MCP that knows about every vault you've configured. Each tool takes a vault parameter (or uses your default), and the router fans out the HTTPS call to the right Obsidian instance.

Why

If you keep more than one Obsidian vault — local or remote, in any combination — you don't want to register a separate MCP server per vault and switch context every time. This router is one process that knows about all of them and routes each tool call to the right one based on a vault parameter.

What you get:

• One install — the Claude Code plugin ships and launches the server (one ~/.claude.json entry on dev setups) → all vaults visible from any Claude Desktop/Code session.
• Local + remote vaults, treated identically. Drop the URL + API key into the config; the router doesn't care where the vault actually runs.
• Cross-vault search: pass vault: "*" to the search tool to fan-out across every vault in parallel.

Capabilities

Tool surface	Coverage
Vault discovery	list_vaults, list_files
Reads	get_file, search, search_smart, get_frontmatter
Writes	write_file, append_to_file, patch_file, delete_file, set_frontmatter, merge_frontmatter — write_file/patch_file/delete_file/merge_frontmatter accept ifMatch (v0.60.0): replay get_file's contentSha256 and the write is refused with a 409 if the file changed since you read it (optimistic concurrency — stops parallel sessions from silently clobbering each other)
File management	move_file (also accepts ifMatch, checked against the source)
Templater	execute_template
Router state	lock_vault, unlock_vaults, set_auto_enrich_mode
Vault provisioning (v0.35+)	plan_vault, provision_vault — defaults-first vault-creation wizard engine
Conversion (v0.11+)	pdf_to_markdown, docx_to_markdown, xlsx_to_markdown, pptx_to_markdown, image_to_markdown, audio_to_markdown, youtube_to_markdown, bing_search_to_markdown, webpage_to_markdown, git_repo_to_markdown, plus pdf_to_markdown_docling (opt-in high-fidelity PDF via Docling, MIT) — port of zcaceres/markdownify-mcp (MIT). Also pdf_to_images (render PDF pages to PNG the model can see) and filter_relevant_blocks (BM25 relevance filter over already-acquired markdown).
Web/page metadata	extract_page_metadata, propose_linked_sources, download_page_assets
Context & graph	get_wiki_context_pack, build_wiki_graph, build_wiki_tour, get_page_neighbors, wiki_path, build_open_link, open_in_obsidian
Cross-vault	every tool accepts vault: "*" for fan-out

Semantic search (search_smart), Templater execution (execute_template) and click-to-open links (build_open_link, open_in_obsidian, the auto-