obsidian-mcp-plugin
The serious version of the Obsidian-to-AI bridge. Instead of Obsidian-as-a-personal-brain, this is Obsidian-as-a-shared-team-brain — it runs an HTTP server so multiple agents (and multiple people's agents) can read and write the same vault concurrently. 40+ tools means your agent can do advanced search, template expansion, and structural edits.
- Teams with 10+ people reading from one shared vault
- Setups where a server and multiple agent clients need the same brain
- Power users who want semantic search and rich tools, not just file read/write
What you'll do
obsidian-mcp-plugin exposes your vault over HTTP, so multiple agents (Claude Code, Cursor, Gemini CLI, your own backend) can all talk to the same brain. Budget 10 minutes.
Before you start
- Obsidian installed
- A vault you want to share
- An agent client that speaks MCP over HTTP (Claude Code ≥ recent versions support this; check your client)
Step-by-step install
- 011. Install the plugin
Obsidian Settings → Community plugins → Browse → search 'MCP plugin' by aaronsb → Install and Enable.
- 022. Start the server
Settings → MCP Plugin → toggle 'Start server'. By default it listens on a local port (typically 27124). The plugin will show the exact URL.
Tip: For team use across machines, you'll need to expose the port via a tunnel (cloudflared, ngrok, Tailscale) or run Obsidian on a shared machine. - 033. Point your agent at the HTTP endpoint
Your MCP client config needs an HTTP transport entry. Exact JSON depends on client; for Claude Code:
{ "mcpServers": { "obsidian-http": { "transport": "http", "url": "http://localhost:27124/mcp" } } }Tip: If your client doesn't support HTTP MCP yet, use obsidian-mcp-tools (stdio) instead. - 044. Restart your client and test
Start a new chat. Ask your agent to list notes. You should see your vault's note titles.
Your first 10 minutes
- 01Try the semantic search: 'find notes similar to our Q3 brand guide'.
- 02Try the template tools: 'create a new SOP using our meeting-notes template'.
- 03Hook up two clients (Claude Code + Cursor) to the same vault. Confirm both see the same changes.
- 04Consider putting the vault on Obsidian Sync or iCloud so it persists across your team's machines.
- 05Add Cognition CLO on top for the retention layer.
Troubleshooting
My agent says the server is not reachable.
Check (a) Obsidian is running, (b) the plugin's server toggle is ON, (c) the URL/port in your client config matches what the plugin shows.
The plugin says 'port in use'.
Something else is on that port. In plugin settings, change the port and update your client config to match.
obsidian-mcp-plugin holds the knowledge. Cognition CLO models retention per employee per concept using a Weibull forgetting curve — so you see decay before it becomes a missed SOP or a failed audit.