coddingtonbear/obsidian-local-rest-api

A secure REST API and Model Context Protocol (MCP) server for your vault.

View on GitHub ↗Jump to charts ↓Open shareable report →

coddingtonbear/obsidian-local-rest-api has 3k+ stars and 350+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 8th, 2026
Created on January 25th, 2022
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 357
Total Stargazers: 3,037 (+0)
Total Subscribers: 17 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.4 hours
Mean response time: 6.6 days
90th percentile: 19.6 days
Tracked items: 68

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 100% of issues opened in the past year have since been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs more discussion (5)
  • bug (2)
  • unconfirmed (2)
  • enhancement (1)
  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Obsidian Local REST API is a plugin that exposes your Obsidian vault through a secure, authenticated REST API and Model Context Protocol server.

The tool solves the problem of integrating Obsidian with external scripts, browser extensions, and AI agents by providing a unified interface to vault operations. It works by running a local server within Obsidian that accepts authenticated requests and translates them into vault operations. The API supports full CRUD operations on notes, surgical patching of specific sections within files (targeting headings, block references, or frontmatter keys), full-text and structured metadata search via JsonLogic, Server-Sent Events streams for vault changes, access to the currently active file, execution of Obsidian commands, tag queries with usage counts, and file opening in the Obsidian UI. Other plugins can extend the API by registering custom routes through a typed extension interface.

Adoption suits developers who need programmatic access to their vault from external tools or who want to integrate Obsidian with AI agents like Claude or Cursor. The tool is particularly valuable for automation workflows, browser extensions that need vault access, and AI-assisted note management. The project includes interactive API documentation and supports multiple MCP client implementations, making it accessible whether you prefer REST calls or the Model Context Protocol.

Development activity shows consistent engagement with the codebase. The project maintains an active extension ecosystem with known extensions registered through its API. Documentation is comprehensive, including a wiki for extension developers and detailed API reference material. The maintainer responds to integration requests from other tools and keeps the MCP protocol implementation current with specification revisions.