list_files_in_vaultLABSCO SUMMARY
Notes written into the right place in the note, not just onto the end of it.
Placing content relative to a heading or a block reference is what makes it usable on a real vault: a summary lands under the section it belongs to and the note keeps its structure.
What it is
A bridge to a running Obsidian instance through the Local REST API community plugin. Seven tools read the vault as it exists right now and write back into it.
What you get
- The vault listed from the root, or a single directory listed on its own (
list_files_in_vault,list_files_in_dir) - The contents of one note read back (
get_file_contents) - A text query searched across every file in the vault (
search) - Content inserted relative to a heading, a block reference or a frontmatter field — placed, not appended (
patch_content) - Content appended to an existing note, or to a new one created for it (
append_content) - A file or directory deleted from the vault (
delete_file)
Requirements
uvx mcp-obsidian on Python 3.11 or newer, plus the Obsidian Local REST API community plugin installed and enabled — that plugin is where OBSIDIAN_API_KEY comes from. OBSIDIAN_HOST and OBSIDIAN_PORT default to 127.0.0.1 and 27124, so you only set them if you moved the plugin. Obsidian has to be running for any of it to answer. One dependency pin to respect: the tool handlers use the mcp 1.x low-level server API, so installing it against mcp 2.0 or newer crashes at import with AttributeError: 'Server' object has no attribute 'list_tools'.
Setup effort
One command plus a key — uvx mcp-obsidian, then supply credentials
USE CASES
01
Summarising a meeting into the note that already exists
Write the summary under the heading it belongs to rather than at the bottom of the file. On a note with a structure you care about, that is the difference between useful and destructive.
02
Capturing something into the vault mid-conversation
Append it to the note you already keep for the topic, or to a new note created on the spot. No app switch, and no inbox file that never gets processed.
03
Finding the note you are thinking of
Search the whole vault for the phrase you half remember, then read the file that comes back. This is what makes the rest usable once the vault is bigger than you can hold in your head.
04
Turning several notes into one document
List the directory, read each note, and write the combined version back into the vault. The source notes stay where they are.
05
Clearing out what you no longer keep
Delete the file or the directory from the vault directly. Worth pairing with a search first, so you delete the one you meant.
7 tools
Listed in project docs. Your client may show a different list.
list_files_in_dirget_file_contentssearchpatch_contentappend_contentdelete_fileBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- uvx on PATH
- Python >= 3.11
- OBSIDIAN_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-obsidianMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp-obsidian": {
"command": "uvx",
"args": [
"mcp-obsidian"
],
"env": {
"OBSIDIAN_API_KEY": "<YOUR_OBSIDIAN_API_KEY>",
"OBSIDIAN_HOST": "<YOUR_OBSIDIAN_HOST>",
"OBSIDIAN_PORT": "<YOUR_OBSIDIAN_PORT>"
}
}
}
}
