obsidian-remote-mcp

A self-hosted MCP server for headless Obsidian vaults. It gives remote AI clients read and write access to a vault over HTTPS without requiring the Obsidian desktop app to be running on the same machine.

This is meant for server environments: home servers, NAS boxes, VPSes, containers, and other setups where your vault lives on disk and you want to expose it through a remote MCP endpoint for apps like Claude.ai. obsidian-remote-mcp is filesystem-backed instead: it works directly from the vault on disk.

The server currently exposes these tools:

| Tool | Description | |------|-------------| | vault_context | Read the vault guidance note configured by VAULT_CONTEXT_PATH, or fall back to AGENTS.md / CLAUDE.md | | vault_read | Full note text (mode full, default) or list one folder level (mode list; path "" = vault root) | | vault_outline | All # headings in a note (one per line); use before vault_read_section | | vault_read_section | Body under a single heading (heading = text without #, case-insensitive) | | vault_frontmatter | Read YAML frontmatter from a note; optional property for a single key | | vault_links | Read outgoing wikilinks and optional backlinks | | vault_create | Create a new note | | vault_update | Replace a note's full contents | | vault_set_frontmatter_property | Set one frontmatter property without rewriting the note body | | vault_edit | Append, prepend, or replace exact text within a note | | vault_trash | Move a note to .trash | | vault_search_title | Find notes by filename (partial or exact); returns paths for vault_read | | vault_search_content | Regex search in note bodies; optional folder to scope large vaults | | vault_daily_note | Read or create a daily note using a configurable path template |

Runtime. The server is TypeScript on Bun. There is no separate b