obsidian-ai-curator

Obsidian AI Curator exposes an MCP server that lets Claude access and manage an Obsidian vault via MCP tools. The server enables natural language queries, automated writing and formatting, file and tag management, and project playbooks, all designed to help you consolidate scattered notes into coherent knowledge. Tools you can expect include vault_scan for scanning vault content, write_note for creating or updating notes with proper formatting, search_content for semantic queries, rename/move operations with link updates, tag analysis and normalization, and daily task capture workflows. Claude can also integrate with Git for checkpoints and rollback, and support automated workflows that connect Claude tasks to repositories and issue tracking. This server is intended to be run locally or in a trusted environment and then referenced by Claude Desktop to expose these capabilities to Claude.

Prerequisites:

• Node.js 18+
• npm (comes with Node.js)
• Access to the Obsidian vault you want to curate

Step-by-step installation:

# 1. Clone the repository
git clone https://github.com/nwant/obsidian-ai-curator.git
cd obsidian-ai-curator

# 2. Install dependencies
npm install

Configuration:

# Create or edit your configuration to point Claude to the MCP server. You will typically use an absolute path to the mcp-server.js file.
# Example (Claude Desktop config):

{
  "mcpServers": {
    "obsidian-vault": {
      "command": "node",
      "args": ["/absolute/path/to/obsidian-ai-curator/src/mcp-server.js"]
    }
  }
}

Run the MCP server:

# Start the MCP server directly (in this repository's context)
npm start

Test that the server is responding by querying Claude for available tools and ensuring the vault is accessible. If you encounter module or dependency issues, reinstall dependencies:

npm install

Tips and common issues:

• Always use absolute paths to your mcp-server.js in Claude Desktop configuration. Relative paths may fail after restarts.
• Ensure your vaultPath in any config.json (used by the Obsidian side) is correct and that you have read/write permissions.
• If Claude reports missing MCP tools, restart Claude Desktop completely after starting the MCP server.
• The server relies on Node.js 18+. If you see module resolution errors, run npm install in the project directory.
• For troubleshooting, consult the repository's docs and TROUBLESHOOTING.md if present, as common issues often relate to path configuration or permission settings.
• When upgrading, re-run npm install to ensure dependencies are up to date.