An Obsidian MCP server lets an AI client search, read and edit notes in your vault — turning Claude into a research and writing partner over your own knowledge base. Setup goes through the Obsidian Local REST API plugin. Here is the path.
Step 1 — enable the Local REST API plugin
In Obsidian: Settings → Community plugins → Browse → "Local REST API", install and enable it. Open its settings and copy the API key. Note the host/port (default https://127.0.0.1:27124). The plugin also now ships a built-in MCP server option, but the standalone server below works with any client.
Step 2 — configure the client
The widely-used mcp-obsidian server connects to that REST API:
{
"mcpServers": {
"obsidian": {
"command": "npx",
"args": ["-y", "mcp-obsidian"],
"env": {
"OBSIDIAN_API_KEY": "your_api_key",
"OBSIDIAN_HOST": "127.0.0.1",
"OBSIDIAN_PORT": "27124"
}
}
}
}
Some implementations are Python (uv) — match the repo you choose. Obsidian must be open (the REST API runs inside the app). Restart the client; see MCP config file location.
Step 3 — verify
Ask: "Search my vault for notes about 'MCP' and summarise what I've written." Real note content back confirms it works.
Common problems
- Connection refused — Obsidian isn't open, or the REST API plugin is disabled.
- TLS/cert errors — the plugin uses a self-signed HTTPS cert; some servers need an "insecure"/http option or the cert trusted.
unauthorized— wrong API key; recopy from the plugin settings.- No tools in client — see Cursor MCP not working.
Going further
Obsidian pairs with web-search and YouTube-transcript servers for a research-to-notes loop. Browse the knowledge category or curated loadouts. Keep the API key private — see MCP security best practices.