This MCP server provides programmatic access to Obsidian vaults via the Obsidian Local REST API plugin, enabling reading, writing, searching, and managing notes through standardized MCP tooling. It supports enhanced capabilities such as multi-vault routing, Claude.ai remote integration, and Tailscale-secured remote access, making it suitable for AI agents and external services to interact with your vaults. Use the supplied Obsidian tools to read and update files, perform global or targeted searches, manage frontmatter and tags, and run advanced Dataview and Task queries across one or more vaults. When targeting specific vaults, include a vault parameter in requests so the server routes each operation to the correct vault instance. The server also exposes health and monitoring scripts for production environments, ensuring reliability in remote or headless deployments.

Prerequisites:

• Node.js (14+ or recommended 18+ LTS)
• npm or yarn
• Access to Obsidian Local REST API plugin configured in your vaults

Installation steps:

1. Clone the repository or download the package
2. Install dependencies npm install

   or

   yarn install
3. Build the project (if applicable, typically compiles TypeScript to dist) npm run build

   or the project’s specific build script

4. Run the MCP server npm start

   or

   node dist/server.js

Configuration:

• Ensure environment variables for security and remote access are set as needed (e.g., MCP_AUTH_KEY, MCP_HTTP_STATELESS for Claude.ai integration).
• If running multi-vault, configure vault connections and ports as described in the project’s docs and your deployment environment.

Verification:

• Send a test MCP request to the running server endpoint, verify authentication, and perform a basic read operation against an Obsidian vault.

Tips and common issues:

• If you enable Claude.ai Remote MCP mode, set MCP_HTTP_STATELESS=true and provide a valid MCP_AUTH_KEY for authentication.
• For multi-vault setups, ensure each vault is reachable and assigned a unique port; the server will route requests based on the vault parameter.
• Use the health-check script and monitor-mcp.sh for production deployments to automatically detect and recover from failures.
• When using Tailscale, ensure network ACLs and certificates are correctly configured to avoid blocked endpoints.
• Review the available Obsidian tool list (obsidian_read_file, obsidian_update_file, etc.) to understand capabilities and required parameters for each operation.