markuspfundstein/mcp-obsidian

MCP server that interacts with Obsidian via the Obsidian rest API community plugin

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 15th, 2026
Created on November 29th, 2024
Open Issues & Pull Requests: 101 (+0)
GitHub issues: Enabled
Number of forks: 503
Total Stargazers: 4,435 (+0)
Total Subscribers: 20 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.1 days
Mean response time: 20.2 days
90th percentile: 73.6 days
Tracked items: 53

Most active contributors

Sign in to see contributor activity.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 66
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 371 days
Stale 30+ days: 61
Stale 90+ days: 59

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

mcp-obsidian is an MCP server that enables interaction with Obsidian vaults through the Obsidian REST API community plugin.

The tool solves the problem of programmatically accessing and manipulating Obsidian notes and vault data from external applications. It works by acting as a bridge between MCP clients and Obsidian, translating requests into REST API calls to the Obsidian REST API plugin, which must be installed and running in Obsidian for the server to function.

Adoption makes sense for developers building AI assistants, automation tools, or integrations that need to read from or write to Obsidian vaults. It suits projects where Obsidian serves as a knowledge base or note repository that external systems need to access programmatically. The tool is particularly relevant for those already using MCP-compatible clients who want to extend their capabilities to include Obsidian vault operations.

The project shows active maintenance with regular commits addressing functionality and bug fixes. Development includes iterative improvements to the MCP server implementation and refinements to how it communicates with the Obsidian REST API. The codebase demonstrates attention to making the integration reliable and usable for downstream applications.