Use case or problem
More and more, we see a desire to interact with our Obsidian Vault via (Gen)AI tooling, from agents to interactive querying, adding notes etc. (Beyond community plugins such as Copilot.) Current approaches either use a coding agent or text editor with such integration.
There are also very many MCP servers built around Obsidian that interact with the files on storage (which then gives them no access to Obsidian commands, and could potentially cause inconsistencies during concurrent editing) or other such methods, but for a user, it is very very difficult to identify which one is useful, will be maintained for the future.
Proposed solution
In addition to the Developer API, Obsidian should include a core plugin that exposes the “canonical” MCP server.
Maybe one of the existing community plugins can be leveraged if licenses allow?
Current workaround (optional)
GitHub - bitbonsai/mcp-obsidian: A lightweight Model Context Protocol (MCP) server for safe Obsidian vault access is a great starting point, though it is limited to file-based access.