Obsidian MCP Pro

What rps321321/obsidian-mcp-pro does

rps321321/obsidian-mcp-pro gives MCP clients access to an Obsidian vault as a structured knowledge and memory system. It covers note discovery, full-text search, frontmatter filtering, aliases, daily notes, recent-file views, vault statistics, and focused content retrieval. Agents can create, append to, prepend, move, rename, and delete notes, as well as update metadata without replacing the note body.

The server also exposes Obsidian’s relationship-oriented features. It can inspect backlinks and outlinks, find isolated or unreferenced notes, detect broken wikilinks, and traverse nearby notes in the vault graph. Canvas files can be listed, summarized, and modified with nodes and directed edges.

How it works

Tools operate against paths relative to the configured vault. Search results include matching paths, line numbers, and snippets, while note reads can be narrowed to a heading path, block reference, or inclusive line range to reduce returned content. Frontmatter and inline tags are parsed for metadata queries and tag operations.

Move operations can update wikilinks, Markdown links, and canvas references across the vault. Deletions go to Obsidian’s .trash folder by default, with a separate permanent-delete option. Bulk or destructive operations use confirmation values such as confirmPath, confirmTag, or a deletion confirmation.

Optional semantic indexing chunks notes, creates embeddings through Ollama or OpenAI, and stores vectors in the vault’s Obsidian cache directory. Indexing requires the explicit confirmation string send-vault-text-to-embedding-provider because readable note content is sent to the selected embedding service.

Setup and configuration

The package can be launched with npx -y obsidian-mcp-pro, which installs the latest published npm release. The runtime requirement is Node.js 24 or newer. The server needs access to an Obsidian vault and can automatically detect the vault in supported configurations.

Folder-scoped access can be restricted with OBSIDIAN_READ_PATHS and OBSIDIAN_WRITE_PATHS. These allowlists are applied during path resolution and can limit which locations tools may read or modify. An Obsidian plugin is also available for running the server inside the app with a settings interface.

Tools and capabilities

• Search notes with ranked, query-centered snippets and line numbers.
• Read full notes or selected sections, blocks, and line ranges.
• Filter notes by frontmatter, tags, aliases, modification time, or folder.
• Create notes, update sections, edit blocks, and merge frontmatter values.
• Create and retrieve daily notes using the vault’s date configuration and templates.
• Rename tags across inline hashtags and YAML tag fields, including nested tags.
• Inspect backlinks, outlinks, orphan notes, broken links, and graph neighbors.
• Read canvases and add text, file, link, or group nodes plus edges.
• Use MCP resources for notes, tags, and the daily note, along with starter prompts for reviews, rollups, action extraction, and Maps of Content.

Limitations and notes

Frontmatter updates preserve keys and values but normalize formatting inside the YAML block, including ordering, comments, quoting, and multiline style. Fragment reads return raw text without the normal frontmatter and tag header. Semantic search is optional and requires an embedding provider; its indexing workflow sends readable note chunks outside the local process. Large canvas responses are bounded, and attachment retrieval has a default 5 MB limit with a 50 MB hard cap.