readNoteLABSCO SUMMARY
It edits where you are, not just where the files are.
Two things separate it from treating the vault as a folder: it can read the note you currently have open, and patchNote inserts relative to a heading or frontmatter field rather than rewriting the file. It goes through the app, so Obsidian has to be running.
What it is
A connection to a running Obsidian through its Local REST API plugin: read notes including the one currently open, list the tree, insert content at a precise anchor, and search with JsonLogic queries.
What you get
- A note read by path
- The note currently open in Obsidian
- Files and folders listed recursively, from the vault root or a folder you name
- Content appended, prepended or replaced relative to a heading, block reference or frontmatter field
- Notes searched with a JsonLogic query
Requirements
Node.js 18 or newer, Obsidian running with the Local REST API plugin installed, and the API key that plugin generates — passed with the host and port it listens on.
Setup effort
Build from source
USE CASES
01
Adding to the note you are looking at
The active note is readable by name, so you do not have to tell the assistant which file you mean.
02
Filing something under the right heading
Content lands under the heading, block or frontmatter field you name, instead of at the bottom of the file.
03
Finding notes by a structured condition
JsonLogic queries express conditions that a plain text search cannot, like a frontmatter field with a particular value.
04
Getting your bearings in a vault
List the tree from the root or one folder, then open the note that looks right.
5 tools
Listed in project docs. Your client may show a different list.
readActiveNotelistNotespatchNotesearchWithJsonLogicBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation. patchNote needs an explicit path; there is no tool to patch the active note directly.
Requires
Node.js 18 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/takuya0206/obsidian-mcp
cd obsidian-mcpInstall dependencies
TERMINAL
npm installBuild the project
TERMINAL
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"Obsidian": {
"command": "node",
"args": [
"/Users/<YOUR_USERNAME>/obsidian-mcp/build/index.js"
],
"env": {
"apiKey": "<YOUR_API_KEY>",
"port": "27123",
"host": "127.0.0.1"
}
}
}
}The path before /obsidian-mcp is the folder you cloned into, and <YOUR_API_KEY> is the API key from Obsidian's Local REST API plugin.
