Obsidian MCP
Provides tools for interacting with Obsidian vaults, including reading notes, accessing the active note, listing files and folders, modifying notes with targeted insertions, and searching notes using JsonLogic queries.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Obsidian MCP read my meeting notes from yesterday"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Obsidian MCP (Model Context Protocol)
Obsidian MCP is a tool that allows you to interact with your Obsidian vault using the Model Context Protocol. This enables AI assistants to read, write, and manipulate notes in your Obsidian vault through a standardized interface.
Prerequisites
Node.js 18 or higher
Obsidian with Local REST API plugin installed and configured
API key generated from the Local REST API plugin
Related MCP server: Obsidian MCP Server Plugin
Setting MCP Server (e.g. Claude Desktop App)
Clone this repository
Install dependencies:
npm installBuild the project:
npm run buildConfigure Claude Desktop App to use this MCP server:
{ "mcpServers": { "Obsidian": { "command": "node", "args": ["/Users/<Your Own Path>/obsisian-mcp/build/index.js"], "env": { "apiKey": "<Your API Token>", "port": "27123", "host": "127.0.0.1" } } } }
Development
Create .env and configure "apiKey", "port", and "host" as mentioned above.
Available Tools
The following tools are implemented:
readNote - Read the contents of a specific note
{ "path": "path/to/note.md" }readActiveNote - Read the contents of the current active note
{}listNotes - Recursively lists files and folders in the entire Vault or under a specified folder
{ "path": "optional/folder/path" }patchNote - Inserts content into an existing note relative to a heading, block reference, or frontmatter field
{ "path": "path/to/note.md", "operation": "append|prepend|replace", "targetType": "heading|block|frontmatter", "target": "target_identifier", "content": "content to insert" }searchWithJsonLogic - Search Obsidian notes using JsonLogic format queries
{ "query": { // JsonLogic query object } }
Available Tools
5 toolslistNotesA
Recursively lists files and folders in the entire Vault or under a specified folder and returns the result as a tree-format string
Inputs: path.
patchNoteC
Inserts content into an existing note relative to a heading, block reference, or frontmatter field.
Inputs: path (required), operation (required), targetType (required), target (required), +4 more.
readActiveNoteB
Read the contents of the current active note
Inputs: no named parameters.
readNoteC
Read the contents of a specific note
Inputs: path (required).
searchWithJsonLogicB
Search Obsidian notes using JsonLogic format queries. Using logical conditions expressed in JSON, you can flexibly filter note metadata and content. Suitable for programmatically generated searches, allowing complex conditions to be expressed in a structured way.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Most tools have distinct purposes: listNotes for browsing, readNote/readActiveNote for reading, patchNote for editing, and searchWithJsonLogic for querying. However, readNote and readActiveNote could potentially be confused as they both read notes, though one targets a specific note and the other the active note, which is clarified in their descriptions.
The naming is mixed: listNotes, readNote, and searchWithJsonLogic follow a verb_noun pattern, but patchNote uses a verb_noun format with a different verb style, and readActiveNote includes an adjective, breaking consistency. While readable, it lacks a uniform convention across all tools.
With 5 tools, the count is reasonable for an Obsidian vault management server, covering core operations like listing, reading, editing, and searching notes. It's slightly lean but functional, as it includes essential CRUD-like actions without being overwhelming.
The tool set covers reading, editing, listing, and searching notes, but lacks explicit create and delete operations for notes, which are common in file-based systems. This creates gaps in full lifecycle management, though patchNote can modify existing notes and agents might work around missing create/delete by other means.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Hosted MCP server for Obsidian Sync vaults: read, search, edit notes. Not affiliated with Obsidian.
A Model Context Protocol server for Wix AI tools
Markdown-based note-taking with a hosted MCP server. Your notes serve you and your AI.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA server implementation that allows AI assistants to read, create, and manipulate notes in Obsidian vaults through the Model Context Protocol.837 npm6MIT
- AlicenseNot gradedqualityDmaintenanceTurns an Obsidian vault into a local Model Context Protocol server that allows AI tools to directly read, search, and write to your notes. It features folder-level access control and a built-in dashboard for easy integration with tools like Claude Desktop and Cursor.7,397 npm2Apache 2.0
- AlicenseAqualityFmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with secure access to Obsidian vaults. Enables reading, writing, searching, and managing notes without requiring Obsidian to be running.507,397 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that provides tools and resources for AI models to interact with an Obsidian vault, enabling file operations, search, and management via the Model Context Protocol.2-