Obsidian Mcp Server
Connect agents to your Obsidian vault through the Local REST API to search notes, edit frontmatter, and maintain a solo-builder knowledge base.
Overview
io.github.cyanheads/obsidian-mcp-server is a Build-phase MCP server that reads, writes, searches, and edits Obsidian notes and frontmatter via the Local REST API.
What is this MCP server?
- Read, write, search, and surgically edit notes, tags, and YAML frontmatter
- Uses Obsidian Local REST API plugin with OBSIDIAN_API_KEY bearer token
- Configurable OBSIDIAN_BASE_URL (default http://127.0.0.1:27123) and HTTPS port option
- Node runtime npm package obsidian-mcp-server v3.2.4 over stdio
- Local-first vault access while Obsidian desktop app runs with the plugin enabled
- Server version 3.2.4
- Default API base http://127.0.0.1:27123
- Required secret OBSIDIAN_API_KEY for Local REST API
Community signal: 581 GitHub stars.
What problem does it solve?
Your best specs live in Obsidian but agents cannot see or update them without manual exports and paste-heavy chat loops.
Who is it for?
Solo builders who run Obsidian with Local REST API and want Claude Code or Cursor to use the vault as agent memory.
Skip if: Teams without Obsidian, headless-only setups with no desktop app, or cloud-note stacks with no local REST bridge.
What do I get? / Deliverables
Agents can search your vault, apply surgical edits, and keep frontmatter consistent while you stay in your normal Obsidian workflow.
- Agent tools to list, read, search, and modify vault notes
- Tag and frontmatter edit operations without full-file rewrites
- stdio MCP connection to http://127.0.0.1:27123 (or HTTPS port)
Recommended MCP Servers
Journey fit
Vault access is Build-phase agent tooling: you give coding agents the same second brain you use for specs, runbooks, and ship checklists. Agent-tooling is the primary shelf because the value is MCP-mediated note CRUD and surgical edits, not publishing docs to end users.
How it compares
Local vault MCP bridge, not a markdown static-site generator or a generic filesystem skill.
Common Questions / FAQ
Who is obsidian-mcp-server for?
Indie developers and writers who keep project knowledge in Obsidian and want MCP agents to read and edit those notes safely.
When should I use obsidian-mcp-server?
Use it during builds and planning when agents should pull context from your vault, update runbooks, or fix tags and frontmatter in place.
How do I add obsidian-mcp-server to my agent?
Enable Obsidian’s Local REST API plugin, copy the API key to OBSIDIAN_API_KEY, register obsidian-mcp-server stdio in MCP config, and keep Obsidian open locally.