Obsidian Local REST API

★ 2.635

Community plugin that starts a local HTTPS server inside Obsidian — since 2026 with a built-in MCP endpoint: read/write notes, search the vault.

Obsidian Local REST API is a community plugin that spins up a local HTTPS server on 127.0.0.1:27124 at startup (self-signed certificate; optionally also HTTP on port 27123, which must be enabled separately). Every request is secured by an API key that you find in the plugin settings and send along as a bearer token. REST endpoints let you read, write, patch, and delete notes (/vault/{path}), edit the currently open file (/active/), full-text search (/search/simple/), run more complex metadata searches via JsonLogic (/search/), list tags, or trigger Obsidian commands (/commands/).

Since 2026, the plugin also ships a built-in MCP endpoint at /mcp/ (streamable HTTP transport, same authentication as the REST API), which provides over 15 tools such as vault_read, vault_write, or search_query. Claude Code natively supports HTTP MCP and can be connected directly to this endpoint via a CLI command — a separate MCP server process is no longer needed. Claude Desktop doesn't speak native HTTP MCP and, per the docs, needs a bridge like mcp-remote for that. This turns your own Obsidian vault into a searchable, writable knowledge source for the agent — all locally on your own machine, without data ever having to leave it.

🔧 SETUP

Install and enable the "Local REST API" plugin via Obsidian Community Plugins
In Obsidian: open Settings → Local REST API, copy the API key, and trust the self-signed certificate if needed
Test reachability: GET https://127.0.0.1:27124/ returns a status check without authentication
Connect Claude Code: `claude mcp add --transport http obsidian https://127.0.0.1:27124/mcp/ --header "Authorization: Bearer <your-api-key>"`
Alternatively enter it manually in `.mcp.json`: `{"mcpServers":{"obsidian":{"type":"http","url":"https://127.0.0.1:27124/mcp/","headers":{"Authorization":"Bearer <your-api-key>"}}}}`

✅ WHEN TO USE IT?

Searching notes while coding

Claude Code searches your Obsidian vault full-text for an old architecture decision while you're working on exactly that module.

Writing insights straight back

After a debugging session, you have Claude write a new note with a summary directly into the vault (vault_write), without opening Obsidian yourself.

⛔ WHEN NOT TO?

No remote access

The server only runs locally on 127.0.0.1 — Obsidian must be running with the vault open on the same machine, otherwise the endpoint isn't reachable.

Better: For access from another device, set up your own tunnel/reverse proxy (not part of the plugin), or work directly on the machine with the vault.

Claude Desktop needs an extra step

Claude Desktop doesn't speak native HTTP MCP; per the docs, a proxy like mcp-remote is needed for that.

Better: Use Claude Code (native HTTP MCP) or configure mcp-remote as a bridge.