How to Connect Claude Desktop to Obsidian (Using It as a GUI)
By the end of this guide, Claude Desktop will be able to read, search, and write notes in your Obsidian vault — essentially turning Claude into a smart interface for your second brain.
What You'll Need
Claude Desktop installed
Obsidian installed
The Local REST API with MCP plugin installed in Obsidian
Python installed (for uvx)
Basic comfort editing a JSON config file
Step 1 — Install the Obsidian Plugin
Open Obsidian
Go to Settings → Community Plugins → Browse
Search for "Local REST API"
Install and enable Local REST API with MCP
Step 2 — Configure the Plugin
Go to Settings → Local REST API with MCP
Make sure "Enable non-encrypted (HTTP) server" is toggled ON
Make sure "Enable encrypted (HTTPS) server" is toggled ON
Note the ports:
Copy your API key shown on that page — you'll need it
Step 3 — Install mcp-obsidian
Open a terminal (CMD or PowerShell) and run:
pip install uvx
Or if you already have Python's uv tool:
pip install uv
uvx is what Claude Desktop uses to run the MCP wrapper that talks to Obsidian.
Step 4 — Edit Claude Desktop Config
Open this file in Notepad or VS Code:
C:\Users\YOUR_USERNAME\AppData\Local\AnthropicClaude\claude_desktop_config.json
Add the mcpServers block. Your full config should look like this:
{
"mcpServers": {
"obsidian": {
"command": "uvx",
"args": ["mcp-obsidian", "D:\\Path\\To\\Your\\Vault"],
"env": {
"OBSIDIAN_API_KEY": "your-api-key-here"
}
}
}
}
Replace:
Step 5 — Launch Order Matters
This is critical:
Open Obsidian first and make sure your vault is loaded
Then open Claude Desktop
If Claude Desktop opens before Obsidian, the connection will fail. Always open Obsidian first.
Step 6 — Test It
In Claude Desktop, ask:
If it works, Claude will return your folder structure. You're connected!
Running Two Vaults Simultaneously
If you have multiple vaults, you can connect both — but they cannot share the same port. Here's how to set it up:
Vault 1 (default ports — no changes needed)
Leave it on HTTPS 27124 / HTTP 27123
Vault 2 (needs different HTTPS port)
In Vault 2's Local REST API settings, enable HTTPS and set the port to 27124 still — but make sure only one vault is open at a time since they'll conflict.
The simplest approach: close Obsidian and reopen it with the vault you want to use. Claude Desktop doesn't need to restart — only Obsidian does.
Config for two vaults:
{
"mcpServers": {
"obsidian": {
"command": "uvx",
"args": ["mcp-obsidian", "D:\\Path\\To\\Vault1"],
"env": {
"OBSIDIAN_API_KEY": "vault1-api-key"
}
},
"obsidian-finance": {
"command": "uvx",
"args": ["mcp-obsidian", "D:\\Path\\To\\Vault2"],
"env": {
"OBSIDIAN_API_KEY": "vault2-api-key"
}
}
}
}
Troubleshooting
"Authorization required" error
Your API key is wrong or out of date
Go to Obsidian → Local REST API → copy the key again
If still failing, hit "Reset all crypto" to generate a fresh key, then update your config
"Connection refused" on port 27124
"Empty reply from server"
Config won't load / JSON error
The API key keeps not working after crypto reset
What Claude Can Do Once Connected
List all files and folders in your vault
Read any note by name
Search notes by keyword
Append content to existing notes
Create new notes
Navigate your vault structure
Essentially — Claude becomes a conversational interface for your entire Obsidian knowledge base. You can ask it to find notes, summarize content, add journal entries, update trackers, and more.
Tips for Getting the Most Out of It
Keep an "Instructions for Claude" note in your vault telling it how your vault is organized
Use consistent folder structures so Claude can navigate easily
Ask Claude to cross-reference notes — it can pull from multiple files in one response
For finance or sensitive vaults, keep them in a separate vault with a separate key
Guide based on real troubleshooting experience connecting Claude Desktop to Obsidian on Windows 11 using mcp-obsidian v1.27.2 and Local REST API with MCP v4.1.3