Obsidian Vault MCP Server
Let Claude Code or Cursor read, search, and work with your Obsidian vault through the Local REST API via MCP.
Overview
Obsidian Vault MCP Server is an MCP server for the Build phase that reads, searches, and interacts with Obsidian vaults via the Local REST API.
What is this MCP server?
- stdio MCP via npx @oleksandrkucherenko/mcp-obsidian (v1.3.3)
- Read, search, and interact with Obsidian notes through Local REST API
- Multi-URL failover via API_URLS JSON array or semicolon-separated list
- Requires Obsidian REST API_KEY plus API_URLS (or legacy API_HOST/API_PORT)
- Obsidian Vault MCP Server branding with published npm package
- npm package version 1.3.3
- stdio transport via npx identifier @oleksandrkucherenko/mcp-obsidian
- 2 required environment variables: API_KEY and API_URLS
Community signal: 13 GitHub stars.
What problem does it solve?
Your agent misses the specs and research locked in Obsidian because there is no standard bridge from the IDE to your vault.
Who is it for?
Solo builders who document in Obsidian and want Claude Code or Cursor to search and reference those notes during build work.
Skip if: Teams without Obsidian, without the Local REST API plugin, or who need cloud-hosted note sync instead of local vault access.
What do I get? / Deliverables
After install, your agent can query and interact with vault notes through MCP while you keep writing in Obsidian as usual.
- Agent-readable access to vault notes and search
- Failover-ready REST URL configuration for multiple endpoints
- Integrated documentation context during coding sessions
Recommended MCP Servers
Journey fit
Obsidian access sits in Build because builders wire their knowledge base into the agent loop while implementing features and maintaining project notes. Docs subphase fits note vaults that hold specs, runbooks, and research the agent must query during development.
How it compares
Obsidian REST bridge MCP server, not a hosted knowledge base or markdown skill pack.
Common Questions / FAQ
Who is Obsidian Vault MCP Server for?
It is for developers who use Obsidian as a personal knowledge base and want MCP agents to read and search that vault via the Local REST API.
When should I use Obsidian Vault MCP Server?
Use it during Build when specs, runbooks, or research live in Obsidian and you need the agent to pull accurate context without manual exports.
How do I add Obsidian Vault MCP Server to my agent?
Configure stdio with npx @oleksandrkucherenko/mcp-obsidian, set API_KEY and API_URLS for your Obsidian REST endpoints, then register the server in your MCP client.