Claude Desktop MCP Integration with Obsidian Vaults

What It Is

Claude Desktop’s Model Context Protocol (MCP) can connect directly to an Obsidian vault, transforming a collection of markdown notes into an AI-accessible knowledge base. The setup involves configuring Claude Desktop to read and write files in the vault directory, then adding custom instructions that teach the AI how to work with the notes.

The system relies on frontmatter metadata - simple key-value pairs at the top of markdown files. A meeting note might include project: alpha and attendees: sarah, which allows Claude to automatically surface related content across different contexts. When someone asks about Project Alpha, the AI pulls up relevant meetings, tasks, and documentation without requiring manual wiki-style links between files.

The configuration lives in Claude Desktop’s MCP settings file, typically found at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS. Developers point the filesystem server to their vault location and optionally create a skills directory containing text files that define how Claude should interact with the notes.

Why It Matters

Most note-taking apps force users into a specific organizational structure - folders, tags, or bidirectional links. This approach flips that model by letting natural language queries handle retrieval. Instead of remembering which folder contains last quarter’s planning notes, users can ask Claude to find “discussions about the API redesign from March.”

The metadata-driven approach solves a common problem with personal knowledge management: information gets buried in daily notes or meeting logs and never resurfaces. A comment about technical debt mentioned in a standup note automatically appears when reviewing the relevant codebase documentation, because both share the same project tag.

For teams already using Obsidian, this eliminates the friction between note-taking and note-finding. The vault becomes a queryable database rather than a filing cabinet. Research teams can track experimental results across months of lab notes. Product managers can connect customer feedback scattered across meeting transcripts to specific feature requests.

The skills directory adds another dimension - persistent context that carries across sessions. Claude can learn project-specific terminology, preferred file structures, or domain knowledge that makes responses more relevant over time.

Getting Started

First, locate the Claude Desktop configuration file. On macOS, edit ~/Library/Application Support/Claude/claude_desktop_config.json. Add an MCP server entry pointing to the Obsidian vault:

{
 "mcpServers": {
 "filesystem": {
 "command": "npx",
 "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/vault"]
 }
 }
}

Replace /path/to/vault with the actual vault location. Restart Claude Desktop for changes to take effect.

Inside the vault, create a .skills directory. Add text files describing how Claude should work with the notes. A file named metadata-rules.txt might contain:

When creating meeting notes, always include:
- date: YYYY-MM-DD
- attendees: comma-separated names
- project: relevant project code
- tags: topical keywords

For frontmatter to work effectively, establish consistent metadata fields across note types. Meeting notes, project documentation, and daily logs should share common fields like project, status, and priority where applicable.

Context

This approach competes with dedicated AI note apps like Mem or Reflect, which build AI features directly into the interface. The MCP method keeps notes in plain markdown, avoiding vendor lock-in. Files remain readable in any text editor, and version control systems like Git work normally.

Limitations include the need for disciplined metadata tagging. Without consistent frontmatter, Claude’s ability to connect related notes degrades. The system also requires Claude Desktop rather than the web interface, limiting accessibility.

Alternative integrations exist through Obsidian community plugins, though most focus on generating content rather than vault-wide search and retrieval. The MCP approach provides deeper filesystem access, allowing Claude to create, modify, and organize files programmatically.

For organizations concerned about data privacy, the local-first architecture keeps notes on the user’s machine. Claude processes queries through Anthropic’s API, but vault contents aren’t uploaded wholesale - only relevant context from specific queries gets transmitted.