mcp-obsidian-advanced

This MCP server provides advanced Obsidian tooling to AI agents, enabling deep inspection and manipulation of your Obsidian vault via the Obsidian Local REST API. It exposes a set of tools for vault analysis, file operations, note management, and vault topology, powered by the obsidiantools library. The tools let you discover the vault tree, analyze note connections with NetworkX, execute Obsidian commands, batch read files with metadata, access the active note, and open files in new leaves. Use these capabilities to let AI agents navigate your vault, perform targeted edits, and generate context-rich content for notes, all while preserving your vault structure and metadata.

Prerequisites:

• A running Obsidian vault with the Obsidian Local REST API plugin installed and configured.
• An API key generated from the Obsidian REST API plugin settings.
• Node.js environment is not required for this deployment since this server runs via uvx; ensure uvx is available on your system.

Installation steps:

1. Ensure environment variables are set for Obsidian access. You can configure via a server config or a .env file as shown in the README example.
2. Start the MCP server using uvx with the provided configuration. Example:

# If using the published configuration example from the README
uvx mcp-obsidian-advanced

3. Validate that the server starts and the Obsidian REST API is reachable at the configured host/port. Typical defaults are host 127.0.0.1 and port 27124, but these can be overridden in the environment variables.
4. If needed, adjust INCLUDE_TOOLS in the environment to limit which tools are exposed to the AI client.

You can also install via Smithery for Claude Desktop automation as shown in the README, which ultimately runs the same underlying uvx-based server:

npx -y @smithery/cli install @ToKiDoO/mcp-obsidian-advanced --client claude

After installation, configure the published servers JSON with your Obsidian API key and vault path as shown in the README.

Tips and caveats:

• The OBSIDIAN_API_KEY and OBSIDIAN_VAULT_PATH are required for the tools to access your vault. Ensure the Vault path is absolute and accessible by the running process.
• Optional environment variables like OBSIDIAN_HOST, OBSIDIAN_PORT, and INCLUDE_TOOLS can be used to tighten scope or relocate the REST API endpoint.
• Some tools rely on the Dataview plugin (e.g., obsidian_recent_changes); ensure the Dataview plugin is installed if you intend to use those features.
• If Claude (or another MCP client) has trouble locating uvx, you can provide the full path to uvx in the server config as noted in the README.
• The environment and config examples show two modes: a published servers configuration (for deployment) and a development/unpublished servers configuration (for local testing).
• When using INCLUDE_TOOLS, provide a comma-separated list of tool names exactly as defined in the tool documentation to enable only those tools.