MCP Connector for Obsidian

Your Obsidian vault, exposed to AI clients over the Model Context Protocol. The MCP server runs inside Obsidian, on loopback, with no binary to download and no cloud round-trip. Claude Desktop, Claude Code, Cursor, Cline, Continue, Windsurf and VS Code all connect to the same endpoint.

What's new in 3.0.0 · Quick start · Tools · Rendered search results · Adaptive tool loading · Per-client tokens · Prompts · Protocol · Clients · Troubleshooting · Security · For developers

---

How it works

Obsidian (Electron)                                 your AI client
┌─────────────────────────────────────┐
│ shared broker, hosted by one vault  │◄──HTTP──►   Claude Code, Codex, Cursor,
│  127.0.0.1:27200/v1/<route-id>/mcp  │  POST only  Cline, Continue, Windsurf,
└──────────────────┬──────────────────┘             VS Code
                   │ forwards by route
┌──────────────────▼──────────────────┐
│ MCP Connector plugin, every vault   │
│  ├─ MCP server (in-process)         │
│  ├─ 64 tools                        │
│  ├─ prompt renderer                 │
│  └─ on-device embeddings            │◄──stdio─►   Claude Desktop
└─────────────────────────────────────┘  via .mcpb shim
   127.0.0.1:27201-27212/mcp

Client configs point at the shared broker on 127.0.0.1:27200. One open vault hosts it inside Obsidian, every open vault registers a route with it, and it forwards each request to that vault's own port. A vault's port can change between restarts without breaking a saved config. If the hosting vault closes, another open vault takes over after a short outage. Details in ADR-0027

Four things follow from that shape:

• Nothing leaves your machine. The server binds to loopback only. Vault reads and writes go through Obsidian's own app.vault and app.metadataCache APIs, so Obsidian's permission model still applies.
• No binary ships from this repo. The server is plugin code running in Obsidian's renderer, which removes the supply-chain surface of downloading and executing a prebuilt executable.
• Semantic search is on-device. Transformers.js runs the embedding model locally. No API key, no Smart Connections requirement.
• Every request carries its own credentials. The transport keeps no session state, which is what makes per-client tool surfaces possible.

What's new in 3.0.0

[!IMPORTANT] 3.0.0 is a major release, and it changes how every client connects. The shared broker now runs inside Obsidian on port 27200 and serves Claude Code, Claude Desktop, Codex, Cursor and the rest from one stable address. Existing Codex entries return 401 until you reinstall them from the new Codex menu. Read Upgrading from 2.x before you update.

Every release is announced on the Obsidian forum thread, where questions and ideas are welcome too.