Obsidian MCP Server

Obsidian MCP Server
Connect Claude to your Obsidian knowledge base through the Model Context Protocol.

Obsidian MCP Server

Connect Claude to your Obsidian knowledge base through the Model Context Protocol.

The Obsidian MCP Server enables Claude to read notes, create content, search your vault, and interact with your personal knowledge management system using natural language.

What Can Claude Do with the Obsidian MCP Server?

The Obsidian MCP Server exposes your Obsidian vault to Claude through the Model Context Protocol.

Core capabilities:

  • Read Notes — Access note contents, frontmatter metadata, and wiki links
  • Create Notes — Generate new notes with proper formatting and metadata
  • Search Vault — Find notes by content, tags, or frontmatter properties
  • Navigate Links — Follow backlinks and explore your knowledge graph
  • Update Notes — Modify existing note content and metadata

Access scope: Claude can only access the Obsidian vault directory you explicitly configure. The integration works with your local Markdown files.

How to Install the Obsidian MCP Server

Installation requires specifying your Obsidian vault directory path.

For Claude Code

Install using Claude Code's MCP management with your vault path:

bash
claude mcp add obsidian npx obsidian-mcp-server /path/to/your/obsidian/vault

Replace /path/to/your/obsidian/vault with the actual path to your Obsidian vault directory.

Important: the commonly used Obsidian MCP servers are community-maintained. Treat the repository you choose as the implementation source of truth rather than assuming Obsidian ships an official MCP package.

For Claude Desktop

Add the server to your claude_desktop_config.json file with your vault path:

Configuration file locations:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Typical configuration structure:

json
{
  "mcpServers": {
    "obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-mcp-server",
        "/Users/username/Documents/ObsidianVault"
      ]
    }
  }
}

Configuration notes:

  • Use the absolute path to your Obsidian vault directory
  • On Windows, use forward slashes: C:/Users/username/Documents/ObsidianVault
  • The vault path should point to the root directory containing your .obsidian folder

Restart Claude Desktop after saving the configuration file.

Obsidian Vault Permission Setup

The Obsidian MCP Server requires filesystem access to your vault directory.

Vault access configuration:

  1. Locate Your Vault Path
  • Open Obsidian
  • Go to Settings → About
  • Your vault path is shown under "Vault location"
  1. Configure Vault Path
  • Use the absolute path to your vault in the MCP configuration
  • Ensure Claude has read and write permissions to this directory
  1. Vault Structure

An Obsidian vault is a folder containing:

  • Markdown files (.md)
  • Assets folder (images, attachments)
  • .obsidian folder (Obsidian settings and plugins)

The MCP Server accesses your Markdown files directly. It does not require Obsidian to be running.

Security considerations:

  • The MCP Server can access all files within your vault directory
  • Subdirectories and nested folders are included
  • Consider vault sensitivity when granting access
  • The server reads and writes Markdown files directly, bypassing Obsidian's interface

Obsidian MCP Use Cases & PKM Examples

Example personal knowledge management workflows that become possible with the Obsidian MCP Server.

Search Your Knowledge Base

Example prompt:

> "Find all notes in my Obsidian vault that mention 'project management' and are tagged with #work."

Claude can search note contents, tags, and frontmatter.

Create New Notes

Example prompt:

> "Create a new daily note for today with sections for Tasks, Meetings, and Notes."

Claude can generate notes with proper Obsidian formatting, including wiki links and tags.

Connect Ideas via Backlinks

Example prompt:

> "Show me all notes that link to my 'Machine Learning' note."

Claude can navigate your knowledge graph through backlinks.

Summarize Notes

Example prompt:

> "Read my note 'Project Alpha Overview' and create a summary with key action items."

Claude can extract information from existing notes.

Generate Content from Templates

Example prompt:

> "Create a new meeting note using my standard template, dated today, for the weekly team sync."

Claude can apply your note templates and populate them with current information.

Organize with Tags and Metadata

Example prompt:

> "Add the tags #review and #priority to my note 'Q1 Goals'."

Claude can update note frontmatter and tags.

Build Reading Lists

Example prompt:

> "Find all notes tagged #to-read and create a reading list sorted by creation date."

Claude can aggregate and organize notes based on metadata.

Note: These are example use cases. The Obsidian MCP Server works with standard Markdown files, so capabilities depend on your vault structure and the MCP server implementation.

Obsidian MCP in a Local Knowledge Vault

Obsidian MCP is a good fit for local-first note systems where agents need to navigate markdown vaults instead of hosted workspaces.

What this shows: This screenshot uses a public Obsidian MCP server repository to show the real shape of note-vault automation and local knowledge workflows.

Why this scenario matters: It makes the local-first value obvious, because Obsidian MCP matters most when an assistant needs to work inside a real markdown vault rather than a hosted workspace.

Typical assistant task: Navigate markdown files, retrieve notes, and support local-first knowledge work without moving into a hosted tool.

Source: Obsidian MCP Repository

When to Pick Obsidian MCP Server vs Notion API

This comparison is most useful when both options look plausible on paper but differ in operating model, team fit, and day-to-day workflow cost.

Decision LensThis Page's MCP PathCompetitor
Best ForLocal-first note systems where markdown files are the durable source of truth.Hosted collaborative workspaces centered on shared pages, databases, and structured team knowledge.
Where MCP WinsObsidian MCP wins when portability, file ownership, and local vault workflows are part of the product requirement.
Tradeoff to WatchIt is not as strong as Notion for teams that need collaborative workspace objects and hosted operational knowledge.
Choose This Path WhenChoose Obsidian MCP for local markdown vaults; choose the Notion API when a hosted knowledge workspace fits better.
Sources

Frequently Asked Questions

Is the Obsidian MCP Server official?
This page covers a community-maintained Obsidian MCP server, not an official Obsidian integration. Obsidian stores notes as local Markdown files, which is why community servers can expose vault content even though Obsidian itself does not ship an official MCP server.
Does Obsidian need to be open?
No. The MCP Server accesses your Markdown files directly. Obsidian does not need to be running.
Will it sync with Obsidian Sync?
Yes. The MCP Server reads and writes files in your vault. If you use Obsidian Sync or another sync service (iCloud, Dropbox), changes will sync normally.
Can it access Obsidian plugins or custom views?
No. The MCP Server works with raw Markdown files. It cannot access Obsidian's plugin system, graph view, or UI-specific features.
What about note encryption?
If your vault uses Obsidian's encryption feature, the MCP Server cannot read encrypted notes. It only accesses plain Markdown files.
Does it work with multiple vaults?
You can configure multiple MCP server instances with different vault paths. Each instance accesses one vault.
Can Claude modify Obsidian settings?
The MCP Server focuses on note content. It typically does not modify .obsidian folder settings, but this depends on implementation.
What if Claude creates invalid wiki links?
Claude can create wiki links ([[Note Name]]) that Obsidian recognizes. However, ensure note names are valid and don't contain special characters that break links.

Use Obsidian MCP in Verdent

Verdent provides streamlined Obsidian integration with simplified vault access configuration. This is Verdent's platform-level integration flow, not the default setup path from community Obsidian MCP implementations.

Connect your Obsidian vault once and access personal knowledge management capabilities across all Verdent projects.

Connect Obsidian Vault in Verdent