Obsidian for Claude: Using Your Vault as Context (Without the Terminal)
Most guides on connecting Obsidian to Claude assume you're in the terminal with Claude Code. But...
Most guides on connecting Obsidian to Claude assume you're in the terminal with Claude Code. But plenty of people use Claude in the browser or desktop app and want the same thing: Claude that can draw on their Obsidian notes. It's possible — it just works differently, and the limits are different too. Here's how.
Can Claude read my Obsidian vault?
Not on its own. Claude in the browser or desktop app doesn't have access to your local files — that's a privacy boundary, not a missing feature. So unlike Claude Code (which reads your vault folder directly), Claude.ai needs a bridge to reach your notes.
That bridge is MCP — the Model Context Protocol, which lets AI tools connect to external data sources through a standard interface. Set up an Obsidian MCP server that exposes your vault, connect it to Claude, and Claude can now search and read your notes as part of a conversation. The notes stay on your machine; the MCP server gives Claude a controlled way to query them.
How do you connect Obsidian to Claude?
The common path:
- Install an Obsidian MCP server — either a dedicated community MCP server for Obsidian, or the Local REST API plugin that exposes your vault over HTTP for an MCP bridge to use.
- Connect it to Claude — register the MCP server so Claude (Desktop, or Claude.ai via a custom connector) can reach it. Claude gains tools to search and read your vault.
- Ask Claude to use your notes — "Based on my notes about the Henderson project, summarize where we left off." Claude queries the vault through the MCP server and answers from your actual notes.
The setup is more involved than Claude Code's open-the-folder simplicity, because you're bridging a local app to a cloud tool. Once it's running, though, Claude can reason over your vault in normal conversation — no terminal required.
What's it good for?
Pulling your own knowledge into Claude conversations. If your vault holds years of notes, research, and decisions, an MCP bridge lets Claude answer from your material rather than general knowledge. "What did I decide about X," "summarize my notes on Y," "what's the history of this project" — grounded in what you actually wrote.
This is retrieval from your knowledge base — useful and real. People describe Claude going from a generic assistant to one that "thinks with" their notes, surfacing forgotten connections across a large vault.
Where does it fall short?
Setup and upkeep. Bridging a local vault to a cloud tool is fiddlier than it sounds, and the bridge has to be running for Claude to reach your notes. It's a maintained setup, not a set-and-forget one.
It's retrieval, not identity. This makes Claude good at answering from your notes. It doesn't give Claude a structured, current understanding of who you are, your role, your active work — unless you've written and maintained all of that in the vault by hand, and keep it current.
It's still Claude-only and vault-bound. The bridge connects one tool to one vault. Your other AI tools don't benefit, and the context is only as fresh and complete as the vault you maintain.
A lighter path for context (vs knowledge)
It's worth separating two goals. If you want Claude to reason over your notes, an Obsidian MCP bridge is the right tool — set it up and use it. If you want Claude (and ChatGPT, and Cursor) to understand who you are and what you're working on without maintaining a vault or running a bridge, that's a context layer's job: it extracts your context from your real sources, keeps it current automatically, and serves it to any tool through MCP.
For many people the realization is that they were using Obsidian to solve the context problem (who am I, what am I working on) when it's really built for the knowledge problem (what do I know). Use it for knowledge, use a context layer for context, and let each do what it's good at.
→ The terminal version: Obsidian for Claude Code
→ The full comparison: Obsidian for AI Context vs a Dedicated Context Layer
→ Give Claude current context without a vault bridge — Unabyss →
