StevenStavrakis/obsidian-mcp

What it solves

It allows AI assistants to safely read and modify Obsidian vaults. By acting as a bridge, it enables LLM-powered tools to interact with your personal knowledge base without requiring the Obsidian application to be open.

How it works

The project implements a local server based on the Model Context Protocol (MCP). It connects to Obsidian vaults by accessing the Markdown files directly on the filesystem. To ensure security, it uses an explicit allowlist of vault paths and strictly validates all file paths to prevent unauthorized access to the rest of the system. It also manages file changes through a transactional system that journals mutations, checks for conflicts using etags, and provides a recovery mechanism for deleted or modified notes.

Who it’s for

Users of Obsidian who want to integrate their notes with MCP-compatible AI assistants to automate note-taking, search, and organization.

Highlights

• Transactional Safety: File mutations are journaled and atomically replaced, with a built-in recovery system for restoring previous versions.
• Comprehensive Toolset: Includes tools for reading, creating, editing, searching, and managing notes, directories, and tags.
• Smart Link Handling: Automatically updates Wikilinks, embeds, and Markdown links when notes are moved or renamed.
• Strict Security: Blocks symlinks, reserves system directories, and rejects invalid paths to ensure the AI cannot access files outside the configured vaults.
• Protocol Support: Compatible with both modern and legacy MCP client versions.