Staying organised in Obsidian can feel like a full-time job, especially when your notes start multiplying across projects, ideas, and domains. Imagine you’re working on a long-term research project. You’ve got dozens of notes scattered across different folders: meeting summaries, article highlights, draft outlines, and to-do lists. Manually curating and connecting them is time-consuming.
Now, imagine asking your AI assistant: “Summarise my notes on cognitive science from last month and create a dashboard of key insights in my Obsidian.” And it does exactly that.
By integrating Claude with Obsidian using the Model Context Protocol (MCP), this kind of interaction becomes possible. Claude can read, organise, and restructure your Obsidian vault, generate summaries, build dashboards, and surface insights, all without leaving your workspace. This guide walks you through setting up the Claude-MCP integration, so your AI assistant becomes a true thinking partner inside Obsidian.
What you’ll learn
Prerequisites
Before we begin, ensure you have:
Let’s get into it
Understanding the architecture
The integration works through a client-server architecture:
When Claude needs to read or write to your Obsidian vault, it sends a structured request through the MCP protocol to the MCP-Obsidian server, which then communicates with Obsidian through its REST API. This architecture allows Claude to perform operations like creating notes, establishing connections, and organising your knowledge base.
Part 1: Setting up Obsidian
Installing the REST API plugin
Obsidian doesn’t have a built-in REST API, so we’ll need to install a community plugin:
Obtaining the API key
Once the REST API plugin is installed:
Part 2: Installing the MCP-Obsidian server
Now we’ll set up the MCP-Obsidian server that will bridge Claude and your Obsidian vault:
or for macOS with Homebrew:
Replace your_api_key_here with the API key you copied from Obsidian.
Part 3: Configuring Claude for MCP integration
Now we’ll configure Claude to connect to the MCP-Obsidian server:
-Replace /opt/homebrew/bin/uv with the path to your uv installation (find it using which uv in the terminal)
-Replace /Users/username/claude-mcp-configs/mcp-obsidian with the path to your cloned repository
-The order of arguments is critical, note the run command comes before the -m mcp_obsidian.main parameter
-If you’re using uvx instead of uv (as in some cases), adjust accordingly
Critical configuration troubleshooting
One of the most common issues (which I personally encountered) is incorrect argument order in the uv command. The correct pattern is:
If you see an error like the unrecognised subcommand '/Users/your/path', it likely means the arguments are in the wrong order. Ensure that the run comes before your script path or module.
Part 4: Testing the integration
After restarting Claude, let’s verify that the integration is working:
If everything worked correctly, you should see the new file in your Obsidian vault. Congratulations! You’ve successfully integrated Claude with Obsidian.
Part 5: Real-world use cases
Vault restructuring and organisation
One of the most powerful applications is having Claude analyse and restructure your Obsidian vault. I’ve used this to:
For example, ask Claude:
Creating dashboard notes
Claude excels at creating dashboards that provide quick access to important information:
This automatically creates a centralised dashboard with:
Implementing organisational frameworks
Claude can help implement and maintain structured organisational frameworks like the PARA method (Projects, Areas, Resources, Archives):
This creates a well-structured vault with:
Template management and consistency
I’ve used the integration to maintain consistent templates throughout my vault:
Claude can then apply these templates consistently across your vault, ensuring standardised note structures.
Part 6: Integration with other MCP servers
The true power of this setup emerges when combined with other MCP servers:
Memory MCP + Obsidian MCP
I’ve found this combination particularly powerful. Memory MCP allows Claude to remember details about your vault structure, preferences, and past interactions across sessions. With both servers enabled:
This allows Claude to:
SequentialThinking MCP + Obsidian MCP
When working with complex vault organisations, adding SequentialThinking MCP enables Claude to:
This is particularly useful when working with large vaults containing technical documentation or multiple projects that require careful organisation and dashboard creation.
Part 7: Advanced tips and best practices
Create a dedicated Claude project
For optimal results, create a dedicated Claude project specifically for Obsidian interaction:
This ensures Claude is proactively using the Obsidian tools whenever appropriate
Security considerations
While the integration is powerful, keep these security considerations in mind:
Path specifications
When working with files in your vault, be clear and specific about paths:
Troubleshooting
Claude can’t find the MCP tools
If the tools icon doesn’t appear or shows fewer than expected tools:
Permission issues
If Claude asks for permission repeatedly or can’t connect:
Path resolution problems
If Claude can’t find or create files at the specified paths:
Conclusion
Integrating Claude with Obsidian via the Model Context Protocol (MCP) turns a personal knowledge base into an intelligent, adaptive system. You get the best of both worlds: Obsidian’s local-first, markdown-based structure and Claude’s ability to interpret, organise, and act on that structure in real-time. This isn’t just about productivity hacks, it’s about scaling your thinking.
With this setup, Claude becomes more than a passive assistant. It actively collaborates with you, restructuring folders based on content patterns, generating context-aware dashboards, auto-tagging new notes, and even maintaining consistent naming conventions across your vault. It reduces friction at every layer of knowledge management.
This integration has reshaped how I work in Obsidian. I now spend more time writing, connecting ideas, and thinking, and less time dragging files, fixing folder chaos, or building manual indexes. Claude automatically surfaces related notes, groups them into logical hierarchies, and keeps evolving the structure as the vault grows.
Over time, the system adapts to your workflow. For instance, it can learn that you prefer project notes grouped by quarter or that you separate deep research from meeting summaries. You can also script custom automation through Claude to generate weekly digests, build project timelines from scattered notes, or convert raw thoughts into structured documentation.
The more you use it, the more it becomes your second brain, organised not by rules, but by understanding.
Resources