The Obsidian MCP server gives Claude full access to your Obsidian vault. Search notes, follow wikilinks, read daily notes, write new ones. For knowledge-management nerds, this is the tightest integration between Obsidian’s structured-but-personal note-taking and Claude’s reasoning.
Why use it
Obsidian is where many second-brain workflows live. The challenge is retrieval: 5,000 notes is a lot to hold in your head. Claude with the Obsidian MCP becomes a librarian for your vault, surfacing what’s relevant and even writing new notes that link to what’s there.
For solo workers maintaining a long-running vault, this is the upgrade that makes the vault feel alive instead of buried.
What it actually does
Search notes by content or tag, read note bodies, list daily notes, follow wikilinks, create new notes, append to existing notes, update frontmatter. The exact surface depends on which Obsidian MCP server you choose.
Practical patterns:
- “Find every note in my vault about deep work and summarize the patterns I’ve recorded.”
- “Create a daily note for today with these meeting notes.”
- “What did I write last month about ContextBolt’s pricing strategy?”
Gotchas
Local REST plugin must be running. If you close Obsidian, the MCP server returns errors until you reopen. Configure Obsidian to start at login if you rely on this daily.
Vault paths are absolute. The MCP only sees the vault Local REST is configured for. If you have multiple vaults, run separate MCP instances or pick the one you use most for AI workflows.
Pair with ContextBolt for two-layer memory: ContextBolt for bookmarks captured automatically, Obsidian for notes you’ve explicitly written. Claude can pull from both in one prompt.
