obsidian

This MCP server integrates Obsidian via MCP to expose Obsidian's note management capabilities to AI assistants and other applications. It wraps core Obsidian operations—such as file creation, reading, updating, deletion, active file management, note search, command execution, and periodic note management—behind the MCP interface so you can issue structured requests and receive consistent responses. The server is designed to work with the MCP Inspector tool during development and testing, enabling you to explore available MCP commands and their payloads in a safe environment before integrating into your app.

Once running, you can utilize the available MCP endpoints to perform tasks like creating or updating notes, reading file content, listing files, performing searches, executing Obsidian commands, and managing daily/weekly/monthly/yearly notes. The Obsidian Local REST API key (OBSIDIAN_API_KEY) is required to authorize requests to the Obsidian instance. Use the MCP Inspector or your own client to craft requests according to the MCP protocol and handle responses in your application logic.

Prerequisites:\n- Node.js 16+ (as indicated by the project badge)\n- npm or yarn for package installation\n- Obsidian Local REST API plugin enabled in your Obsidian workspace and an API key generated for access\n\nInstallation steps:\n1) Install dependencies:\n npm install\n\n2) Build the TypeScript project (if applicable):\n npm run build\n\n3) Run the MCP server via the Inspector (environment variable required for Obsidian API key):\n OBSIDIAN_API_KEY=your-api-key npm run inspector\n\n4) Verify the MCP server is running and reachable via the MCP inspector or your client. You should see the server registered under the name you provide (e.g., obsidian).

Tips and notes:\n- Ensure the OBSIDIAN_API_KEY environment variable is set with a valid key for your Obsidian Local REST API plugin.\n- The server path in mcp_config should point to your built server bundle (e.g., dist/server.js); adjust if your build outputs to a different location.\n- If you upgrade Node.js or dependencies, re-build the project to ensure compatibility.\n- Use the MCP Inspector during development to discover available commands and payload shapes before integrating into your application.\n- Common issues include incorrect API keys, network access restrictions, or mismatched Obsidian plugin versions; verify the Local REST API plugin is running and accessible from the MCP server host.