← all repositories
coddingtonbear/obsidian-local-rest-api

Your Obsidian vault, now with an API and an MCP port

An Obsidian plugin that exposes your notes to scripts, browser extensions, and AI agents via REST and the Model Context Protocol.

2.4k stars TypeScript AgentsCoding Assistants
obsidian-local-rest-api
Velocity · 7d
+1.5
★ / day
Trend
steady
star history

What it does

This plugin turns your Obsidian desktop app into a local HTTPS server with two doors: a REST API and a built-in MCP server. Scripts, browser extensions, and AI clients can read, write, search, and patch notes without touching the filesystem directly. Everything is gated behind API-key auth and a self-signed certificate.

The interesting bit

The surgical PATCH is the quiet star. You can append to a heading, replace a frontmatter field, or target a block reference without rewriting the whole file. For AI agents, the MCP server means Claude, Cursor, or any Streamable HTTP client can manipulate your vault through structured tools rather than raw HTTP calls.

Key highlights

  • Full CRUD on any vault file, including binary assets
  • Targeted edits via heading, block, or frontmatter selectors (headers or URL segments)
  • Built-in MCP server at /mcp/ with dedicated tools for vault operations, search, and periodic notes
  • JsonLogic queries for structured metadata search
  • Periodic note support (daily, weekly, monthly, quarterly, yearly)
  • Extensible: other plugins can register custom routes

Caveats

  • HTTPS uses a self-signed certificate; clients must trust it or fall back to HTTP on port 27123
  • MCP setup varies by client and may require mcp-remote bridging for Claude Desktop
  • The README truncates the tools list mid-sentence, so the full MCP surface isn’t fully visible

Verdict

Worth installing if you automate your note-taking or want AI agents that actually know what’s in your vault. Skip it if you treat Obsidian as a sealed garden and like it that way.

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.