How to Install the Obsidian MCP in Claude Code (2026)
A. Frans
Published June 11, 2026
Table of Contents
Your Obsidian vault is years of notes Claude can't see. The Obsidian MCP server fixes that, it gives Claude Code read and write access to your vault, so you can ask it to search your notes, summarize a project folder, draft a new note from a conversation, or link ideas across files you'd forgotten you wrote. This walks through the install, the security setup that actually matters, and the workflows that justify the effort.
Setup takes about ten minutes if Claude Code is already installed. Here's the whole path before the detail.
| Step | What you do | Time |
|---|---|---|
| 1 | Confirm Claude Code is installed | 1 min |
| 2 | Pick an MCP server and prep your vault | 2 min |
| 3 | Run the install command | 2 min |
| 4 | Configure vault path and permissions | 3 min |
| 5 | Test with a read-only query | 2 min |
Before you start
You need Claude Code installed and an Obsidian vault on the same machine. Check Claude Code first:
claude --version
If that returns a version, you're set. If not, install it from the official docs (claude.com/claude-code) and come back.
Now find your vault's path. In Obsidian, open Settings, go to "About," and note the vault location, or right-click the vault folder in your file manager and copy its full path. You'll need it in step 4. On a Mac it's often something like /Users/you/Documents/MyVault; on Windows, C:\\Users\\you\\Documents\\MyVault.
Step 1, choose your MCP server
There's more than one Obsidian MCP server, and the choice matters for how it talks to your vault.
The simplest approach reads and writes the vault's markdown files directly on disk. It needs no plugin inside Obsidian and works even when Obsidian is closed, since it's just operating on files. This is the most reliable option for most people.
The other common approach talks to Obsidian through its Local REST API community plugin. That route gives Claude access to Obsidian's live state, open notes, the active file, search powered by Obsidian's own index, but it requires the plugin running and Obsidian open. Pick this only if you specifically want live-app features.
For most users, start with the direct-file-access server. It's fewer moving parts and keeps working whether or not the app is open.
Step 2, back up your vault first
This is the step people skip and regret. The MCP server will have write access to your notes, which means a misunderstood instruction could overwrite or delete a file. Before you connect anything:
# Copy your vault to a backup folder first, never skip this
cp -r "/path/to/MyVault" "/path/to/MyVault-backup-2026-06-11"
If you use Obsidian Sync, version history, or git on your vault, you have a safety net already, but a fresh copy costs nothing and saves a bad afternoon. Do it.
Step 3, install the server
The install pattern with Claude Code's MCP command looks like this:
claude mcp add obsidian -- npx -y obsidian-mcp /path/to/MyVault
Replace /path/to/MyVault with your actual vault path from before. The npx -y part pulls the server package and runs it without a separate global install.
Important: package names and exact arguments differ between the available Obsidian MCP servers, so confirm the current command on the specific project's GitHub README before running it. Search "Obsidian MCP server GitHub," read the README of the one you picked, and use its documented install line. Don't trust a command from an old article (including the shape above) over the project's own docs, these packages get renamed and updated.
If your server uses the REST API plugin route instead, you'll install the "Local REST API" plugin in Obsidian, copy its API key, and pass that key to the MCP server as an environment variable rather than passing a file path. The README will spell out which model it uses.
Step 4, scope permissions and confirm the path
Once added, Claude Code lists the server in your MCP config. Verify it:
claude mcp list
You should see obsidian and its status. Now think about scope. The single most important security decision is which folder you point the server at. If you give it your entire vault, Claude can read and write everything, including private journals, financial notes, and anything else you keep there.
If part of your vault is sensitive, point the server at a subfolder instead of the root, or keep sensitive material in a separate vault the MCP server never touches. Least privilege applies to your own notes too. You can run the server against a "work" folder and leave "personal" out of reach entirely.
Step 5, test read-only before you trust writes
Open Claude Code and start with a query that only reads:
Search my Obsidian vault for notes about [a topic you know exists] and summarize what I've written.
If it pulls real content from your notes, the read path works. Then test a careful write:
Create a new note called "MCP Test" in my vault with a one-line body, then tell me the file path.
Check that the note appears in Obsidian where you expect. Once both directions work and land in the right place, you're connected. If a write lands in the wrong folder or format, fix the configuration now, before you start trusting it with real notes.
What this actually unlocks
The point isn't the connection, it's what you do with it. A few workflows that earn their keep:
Search across years of notes by meaning, not just keywords — "find where I wrote about pricing strategy" surfaces notes even when they don't contain that exact phrase, because Claude reads them. Turn a long Claude conversation into a permanent note in your vault, formatted with your own linking conventions. Summarize a sprawling project folder into a single status note. Find orphan notes and suggest links between related ideas, the connective work that makes a vault useful and that nobody has time to do by hand.
For people who've built a real second brain in Obsidian, this closes the loop: the notes stop being a write-only archive and become something you can actually query and extend in conversation.
The security reality, stated plainly
You're giving an AI write access to your personal knowledge base. That's powerful and it's worth respecting. Three rules keep it safe: back up before you connect (covered above), scope the server to only the folders it needs, and review writes until you trust the setup. The MCP server runs locally and operates on your files on your machine, nothing is uploaded by the connection itself, but Claude does read the note contents it works with, so keep genuine secrets (passwords, keys) out of any vault you connect, the same way you would with any tool. Check the GitHub repo of whichever server you chose for its specific security notes; the maintainers document the exact permissions their version requests.
FAQ
Does Obsidian need to be open for the MCP server to work?
It depends on the server. The direct-file-access servers operate on your vault's markdown files on disk, so they work whether Obsidian is open or closed. Servers that use the Local REST API plugin need Obsidian running, because they talk to the live app. For always-available access, choose a file-based server.Is the Obsidian MCP server free?
The MCP servers themselves are open source and free. Your only requirement is Claude Code and a Claude subscription. There's no separate fee for connecting your vault. Check the specific server's GitHub repository to confirm its license and any optional paid components.Can the MCP server delete or overwrite my notes?
Yes, if you grant write access, which is exactly why you back up first and test with read-only queries before trusting writes. A misread instruction can modify the wrong file. Back up the vault, scope the server to non-sensitive folders, and review what it writes until you're confident in the setup.Which Obsidian MCP server should I use?
For most people, a direct-file-access server is the simplest and most reliable choice, fewer moving parts and it works with Obsidian closed. Choose a REST-API-based server only if you specifically need live-app features like the active note or Obsidian's own search index. Compare the options on GitHub and read each README before deciding.Will this upload my notes to the cloud?
The MCP connection itself runs locally and doesn't upload your vault. But Claude reads the contents of the notes it works with to answer you, the same as any file you share with an AI assistant. Keep passwords and regulated data out of any connected vault, and point the server only at folders you're comfortable having Claude read.Share this article
⚙Related Tools
📄Related Articles
Get More AI Tool Guides
New comparisons and guides every week. Join thousands of professionals staying ahead of the AI curve.