All How-To Guides

3 Ways to Use Obsidian with Claude Code

How to use Obsidian with Claude Code?

3 MCP servers featured

Last reviewed June 2026

Obsidian is a powerful knowledge management tool with local Markdown files. MCP servers can connect Claude to your Obsidian vault for note access, search, and knowledge retrieval. Here are the best options for Obsidian integration.

Recommended MCP Servers

Obsidian MCP

MarkusPfundstein/mcp-obsidian

>3k

Connect to Obsidian vaults via the Local REST API for note reading and writing.

Key Features

  • Read and write notes
  • Search vault contents
  • Access note metadata
  • Create and update notes

Installation

npx obsidian-mcp

The Obsidian MCP provides comprehensive vault access through the Local REST API. Search your knowledge base, read notes, and create new content. Perfect for using Obsidian as Claude's memory.

Best for: Obsidian power users View on GitHub

Filesystem MCP

anthropics/mcp-server-filesystem

>2k

Direct access to Obsidian vault files since they're just Markdown.

Key Features

  • Direct file access
  • Read any note
  • Create and edit notes
  • Works with any vault

Installation

npx @modelcontextprotocol/server-filesystem /path/to/vault

Since Obsidian vaults are just folders of Markdown files, the Filesystem MCP works directly. No Obsidian plugin required—just point it at your vault folder. Simple and effective.

Best for: Basic vault access View on GitHub

Obsidian MCP Server

cyanheads/obsidian-mcp-server

>300

Native Obsidian plugin that exposes vault as an MCP server.

Key Features

  • Native plugin integration
  • Vault search
  • Note operations
  • Obsidian API access

Installation

Install via Obsidian Community Plugins

This Obsidian plugin runs an MCP server directly from within Obsidian. Install it like any community plugin for seamless integration. Good for users who prefer native Obsidian solutions.

Best for: Plugin-based workflows View on GitHub

Quick Comparison

MCPStarsBest ForProsCons
Obsidian MCP>2.7kPower usersFull API accessREST API required
Filesystem MCP>2kSimple accessNo plugin neededLimited features
Obsidian MCP Server>300Native integrationObsidian-nativePlugin management

Getting Started

To use Obsidian with Claude Code:

  1. For simple access, use Filesystem MCP with your vault path:

    npx @modelcontextprotocol/server-filesystem /path/to/obsidian/vault
    
  2. For full integration, install the Obsidian Local REST API plugin and the Obsidian MCP.

Example prompt: "Search my Obsidian vault for notes about project management and summarize the key points."

Related Guides

Frequently Asked Questions

Which MCP server connects Claude to Obsidian?

The most popular is MarkusPfundstein/mcp-obsidian, a Python server run with 'uvx mcp-obsidian'. cyanheads/obsidian-mcp-server is a richer Node alternative run with 'npx obsidian-mcp-server'. Both talk to your vault through the Obsidian Local REST API community plugin. Alternatively, the official filesystem MCP reads vault files directly with no plugin required.

Can Claude read my Obsidian vault?

Yes. With an Obsidian MCP server connected, Claude can list, read, and full-text search notes across your vault, then summarize or answer questions using that content. REST-API-based servers reach notes through the Local REST API plugin, while the filesystem MCP reads the underlying Markdown files directly, since an Obsidian vault is just a folder of .md files.

Can Claude create and edit notes in Obsidian?

Yes. Obsidian MCP servers expose write tools, so Claude can create new notes and edit existing ones. mcp-obsidian supports append and patch operations that insert content relative to a heading, block, or frontmatter field. cyanheads/obsidian-mcp-server adds edits to sections, tags, and frontmatter. The filesystem MCP can also create and overwrite note files directly.

Is it safe to give Claude access to local Obsidian files?

It is reasonably safe if you scope access. The filesystem MCP only reaches directories you explicitly pass to it, so point it at one vault folder. REST-API servers require an API key you generate in the Local REST API plugin and listen only on localhost. Everything runs locally with your user permissions, so grant write access only to vaults you trust.

Keep Exploring

WebMCP Developers