This project provides an MCP server that integrates with Obsidian, enabling large language models (LLMs) like Claude to interact with a user's Obsidian vault. It allows LLMs to list files, retrieve content, search notes, and modify existing files, acting as a bridge between AI and personal knowledge management systems.

How It Works

The server leverages the Obsidian Local REST API community plugin to communicate with the Obsidian vault. It exposes a set of tools that LLMs can call, such as list_files_in_vault, get_file_contents, search, patch_content, append_content, and delete_file. This structured approach allows LLMs to perform complex knowledge management tasks programmatically.

Quick Start & Requirements

• Install Obsidian REST API: Install and enable the Obsidian Local REST API community plugin within Obsidian.
• Configuration: Configure the OBSIDIAN_API_KEY and OBSIDIAN_HOST via a .env file or server configuration.
• MCP Inspector: Recommended for debugging via npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-obsidian run mcp-obsidian.
• Logs: Server logs can be monitored at ~/Library/Logs/Claude/mcp-server-mcp-obsidian.log.

Highlighted Details

• Supports file listing, content retrieval, search, and modification (patching/appending).
• Enables LLMs to create new notes from summarized content.
• Provides specific tools for interacting with Obsidian's structure (headings, block references, frontmatter).

Maintenance & Community

The project is maintained by MarkusPfundstein. Further community or roadmap information is not detailed in the README.

Licensing & Compatibility

The README does not explicitly state a license. Compatibility for commercial use or closed-source linking is not specified.

Limitations & Caveats

The README does not detail specific limitations, known bugs, or deprecation status. Debugging MCP servers over stdio is noted as challenging, with the MCP Inspector recommended as a solution.