Two things separate this from a filesystem server pointed at a vault: obsidian_manage_frontmatter changes metadata atomically instead of rewriting the note, and obsidian_dataview_query lets the assistant ask the same questions your dashboards ask. The multi-vault mode routes by a vault parameter, so one server can hold work and personal side by side without mixing them.
An Obsidian vault server that talks to the Obsidian Local REST API plugin over HTTP. This fork adds multi-vault routing, a stateless HTTP mode for Claude.ai's remote connectors, and query tools for Dataview and the Tasks plugin.
- obsidian_read_file — a note's content and metadata, as markdown or JSON, with case-insensitive path fallback
- obsidian_update_file — append, prepend or overwrite, targeting a path, the active note, or a periodic note
- obsidian_search_replace — string or regex search and replace inside one note
- obsidian_global_search — text or regex across the vault, filtered by path and modification date, paginated
- obsidian_list_files — files and subfolders in a folder, filtered by extension or name regex, as a tree
- obsidian_manage_frontmatter — get, set or delete YAML keys without rewriting the whole file
- obsidian_manage_tags — add, remove or list tags in both frontmatter and inline content
- obsidian_delete_file — remove a file from the vault
- obsidian_dataview_query — run TABLE and LIST DQL queries against the vault
- obsidian_task_query — search tasks by status, date range and priority, in table, list or summary form
Obsidian with the Local REST API plugin enabled, and its API key. For a single vault set OBSIDIAN_API_KEY and OBSIDIAN_BASE_URL; for several, pass a JSON array in OBSIDIAN_VAULTS with an id, apiKey and baseUrl per vault. Remote access through Claude.ai also needs MCP_AUTH_KEY. Runs over stdio or HTTP; set MCP_HTTP_STATELESS to true for Claude.ai compatibility.