obsidian_delete_active
Deletes the currently-active file.
LABSCO SUMMARY
Notes get edited in place instead of rewritten whole.
The patch tools are what separate this from a file-writing server: content goes in relative to a heading, block or frontmatter target, so appending to today's note does not mean reading it, rebuilding it and putting it back. Everything routes through the running app, which is also the constraint — the vault has to be open, and the active-file tools follow whichever tab was last touched rather than a path you chose.
What it is
A server over a running Obsidian vault with 24 tools, addressing three targets — the active file, a periodic note by period, or any vault file by name.
What you get
- The same four writes on each target: append, replace the whole content, patch relative to a heading, block or frontmatter target, and delete
- Periodic notes addressed by period rather than by filename, so today's daily note is written without resolving its path first
- Vault listing at the root or inside a directory, file read by name, and create-or-replace through obsidian_put_file
- Three searches with different reach: plain text with a contextLength, a Dataview query, and a JsonLogic query
- Obsidian's own command palette, with obsidian_get_commands listing the command IDs and obsidian_execute_command running one — which covers what the other tools do not
- obsidian_open_file to bring a note up in the app, optionally in a new leaf
Requirements
Obsidian running with the vault open — every tool acts on that vault, on its currently-active file, or on its command list. MIT licensed.
Setup effort
One command plus a key — bunx @fazer-ai/mcp-obsidian@latest, then supply credentials
USE CASES
01
Adding to today's note without opening it
Address the daily note by period, read what is already there, and patch the new line in under the right heading instead of appending to the bottom of the file.
02
Tracking down where a decision was written up
Start with a text search wide enough to catch a paraphrase, tighten with a Dataview query when the notes carry structure, then pull the file that matched.
03
Filing a new note in the right folder
Look at what is already in the directory so the new file matches its neighbours, write it, and open it in the app for the edit that follows.
04
Editing the note already on screen
Read the active file, insert into it at a target rather than at the end, and replace it outright only when the rewrite is the point.
05
Reaching a vault feature the tools do not cover
List the command IDs Obsidian exposes and run one of them, which is how plugin actions with no tool of their own get triggered.
24 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
obsidian_delete_file
Deletes a file in the vault.
obsidian_delete_periodic
Deletes the periodic note for a given period.
obsidian_execute_command
Executes a specified command.
obsidian_get_active
Returns the content of the currently-active file.
obsidian_get_commands
Returns a list of available commands.
obsidian_get_file
Returns content of a vault file.
obsidian_get_periodic
Returns the periodic note for a given period.
obsidian_list_vault_directory
Lists files in a specified directory.
obsidian_list_vault_root
Lists files in the root of the vault.
obsidian_open_file
Opens a file, optionally in a new leaf.
obsidian_patch_active
Inserts content into the active file relative to a target.
obsidian_patch_file
Inserts content into a vault file relative to a target.
obsidian_patch_periodic
Inserts content into a periodic note relative to a target.
obsidian_post_active
Appends content to the active file.
obsidian_post_file
Appends content to a vault file.
obsidian_post_periodic
Appends content to the periodic note.
obsidian_put_active
Replaces content of the active file.
obsidian_put_file
Creates or replaces a vault file.
obsidian_put_periodic
Replaces content of the periodic note.
obsidian_search_dataview
Searches using a Dataview query.
obsidian_search_json_logic
Searches using a JsonLogic query.
obsidian_simple_search
Searches for text in vault with optional context.
obsidian_status
Returns basic details about the server.
BEFORE YOU INSTALL
What to know first
Tools you get
24 tools when we connected. Post appends, put replaces the whole note, patch inserts relative to a heading or front-matter field, and delete removes the note. obsidian_execute_command can run any Obsidian palette command.
Requires
- bunx (Bun) on PATH
- Obsidian running, with the Local REST API community plugin installed and enabled
- OBSIDIAN_API_KEY, copied from the Local REST API plugin's settings in Obsidian
CONTEXT COST
Light Standing cost
Rated by the size of the 24 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
bunx @fazer-ai/mcp-obsidian@latestMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"@fazer-ai/mcp-obsidian": {
"command": "bunx",
"args": [
"@fazer-ai/mcp-obsidian@latest"
],
"env": {
"OBSIDIAN_API_KEY": "<YOUR_OBSIDIAN_API_KEY>"
}
}
}
}<YOUR_OBSIDIAN_API_KEY> is the API key shown in the Local REST API plugin's settings in Obsidian. The plugin has to be installed and enabled, and Obsidian running, for any tool to work.
Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · TERMINAL
git clone https://github.com/fazer-ai/mcp-obsidian
cd mcp-obsidian
bun installAdd this block; <YOUR_PATH_TO_REPO> is the absolute path of your clone and <YOUR_OBSIDIAN_API_KEY> the key from the Local REST API plugin's settings:
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"@fazer-ai/mcp-obsidian": {
"command": "bun",
"args": [
"<YOUR_PATH_TO_REPO>/src/index.ts"
],
"env": {
"OBSIDIAN_API_KEY": "<YOUR_OBSIDIAN_API_KEY>"
}
}
}
}
