mcp-obsidian-cli
This server lets you capture, search, update, and organize Obsidian vault notes from chat by exposing the Obsidian CLI as MCP tools.
Create notes: plain notes with
obsidian_create, or Templater-template notes with placeholder expansion viaobsidian_create_from_template.Daily notes: read, append to, and get the path of today's daily note.
Read notes: by file name (wikilink-style) or exact vault path.
Search and discovery: full-text search with context, list files by folder/extension, list tags with counts, list backlinks, query tasks, list recently opened files, and list heading outlines.
Properties: read frontmatter properties or set them, including list/multi-valued properties via JSON-array values.
Organize: move or rename notes, and delete notes to trash or permanently.
Templates: read template contents and optionally resolve their variables.
Execute Obsidian commands: trigger any core or plugin command by its command ID.
Full CLI access: run any of the 80+ Obsidian CLI commands through the generic
obsidianpass-through tool, with built-in help and intent-to-verb guidance.
Requires Obsidian running with its command line interface enabled; the server handles vault targeting via config or environment variables.
Provides tools for creating, reading, searching, and managing notes in an Obsidian vault, including daily notes, tags, tasks, backlinks, and templates.
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., "@mcp-obsidian-cli Search my vault for 'project ideas' and return results."
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.
mcp-obsidian-cli
Your thinking starts in Claude Desktop, not in Obsidian. You research, draft, argue with the model, and when something's worth keeping you say "save this to my vault." It lands in the right place: your template, your properties, today's daily note, wired into your link graph. No tab-switch, no copy-paste.
Installing this? Start at Install. One prompt in Claude Code handles the whole setup.

Two halves:
Capture — turn a conversation into a real note, filed where it belongs.
Augment — pull what's already in the vault (backlinks, full-text search) back into the chat to inform or update a note.
Needs Obsidian running. It can sit minimized, so you never switch to it.
Using this from Claude Code? The native obsidian-cli skill fits better there: direct CLI, no MCP layer. Installing is separate. The prompt below runs in Claude Code.
Install
Run the prompt below in Claude Code. It checks Node, enables the Obsidian CLI, writes your Claude Desktop config, and verifies the connection. Only hand-edit the config if that path fails.
Fetch https://raw.githubusercontent.com/stonematt/mcp-obsidian-cli/master/docs/INSTALL.md
and follow it end to end to install the mcp-obsidian-cli MCP server for my Claude Desktop.
Ask me for my Obsidian vault name and folder path, then handle everything else — check Node,
enable the Obsidian CLI, edit my Claude Desktop config, and verify it works.Full walkthrough, including failure modes: docs/INSTALL.md.
Run the server directly. This starts the server in your terminal and installs nothing:
npx mcp-obsidian-cliRelated MCP server: Obsidian MCP Server
Requirements
The install prompt checks each of these. Listed here for reference:
Obsidian running with its command line interface enabled (Settings → General → Advanced → Command line interface). The CLI ships built into Obsidian — nothing extra to install.
obsidian-clireachable. macOS auto-detects it inside the Obsidian app bundle, so there is nothing to configure. Linux and Windows have no auto-detection: pointOBSIDIAN_CLI_PATHat the binary yourself.Node.js >= 18
How it works
The server exposes Obsidian CLI commands as MCP tools. A generic pass-through tool handles the full CLI surface (80+ commands), plus typed convenience tools for common operations:
Tool | Description |
| Generic pass-through — run any CLI command (ships intent→verb cheatsheet, pre-call manifest validation, reload detection) |
| Manifest-backed help — list verbs by category, or look up a single verb / doc topic |
| Read today's daily note |
| Append to daily note |
| Read a note by name or path |
| Full-text search with context |
| List tags with counts |
| Query tasks (daily, todo, done) |
| Read frontmatter properties |
| Create a new plain note (no Templater expansion) |
| Create a note from a Templater template (expands |
| Set a frontmatter property |
| List backlinks to a note |
| List vault files |
| Recently opened files |
The generic obsidian tool means the MCP server never falls behind the CLI — new CLI commands work immediately without a server update.
What it can do
It talks to the running Obsidian instance, so it works with your vault the way Obsidian sees it:
Backlinks and full-text search across your resolved link graph and search index (the augment half).
Templater templates and typed frontmatter properties when creating or updating notes.
Daily notes, task queries, and tag counts.
80+ commands through the generic pass-through. No API keys, no REST plugin. Just the official Obsidian CLI.
Automated installers should use the prompt under Install, which handles vault name, CLI path, and verification. This block is the hand-edit fallback.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"obsidian": {
"command": "npx",
"args": ["-y", "mcp-obsidian-cli"],
"env": {
"OBSIDIAN_VAULT": "my-vault"
}
}
}
}Environment variables
Variable | Default | Description |
| (none) | Target vault by name |
|
| Path to CLI binary |
|
| Command timeout |
|
| Base path for config file |
Config file
The server can read settings from a YAML config file:
Default:
~/.config/mcp-obsidian-cli/config.yamlWith
XDG_CONFIG_HOME:$XDG_CONFIG_HOME/mcp-obsidian-cli/config.yaml
Config file format:
vault: "my-vault"
cliPath: "obsidian-cli"
timeoutMs: 15000Config precedence: env vars > config file > hardcoded defaults
Bugs / requests
File an issue: https://github.com/stonematt/mcp-obsidian-cli/issues/new/choose. Bug template asks for version, MCP client, tool call, and response — quick to fill, fast to act on.
License
MIT
Maintained by @stonematt Licensed under the MIT License
Trademark Notice: "Obsidian" is a trademark of Obsidian Publishing, Inc. This project is not affiliated with or endorsed by Obsidian Publishing.
Available Tools
23 toolsobsidianA
Run any Obsidian CLI command. Pass the full command string exactly as you
would on the terminal (minus the leading 'obsidian' binary name). Leading
vault=NAME overrides the active vault and is cached for subsequent calls.
Intent -> verb cheatsheet. Use the canonical verb on the right; the convenience
tools (obsidian_*) wrap the same verbs with typed args.
PUT put new note from template -> templater:create-from-template template=… file=… create plain note -> create path=… content=… append to today's daily -> daily:append content=… GET read note -> read path=… (or file=…) search content -> search:context query=… [path=… limit=…] list properties / read one -> properties [file=…] | property:read name=… file=… list backlinks -> backlinks file=… MOVE/RENAME move or rename note -> move file=… to=… (or path=…) DELETE delete note -> delete path=… DISCOVER list files -> files [folder=… ext=…] list tags with counts -> tags counts [sort=name|count] list tasks -> tasks [daily todo done path=…] recently opened -> recents CLI reference -> help [verb]
If you don't see the intent here, the CLI's help verb is the source of truth.
Inputs: command (required).
obsidian_backlinksA
List backlinks to a note.
Parameters: file (optional) — note name (wikilink resolution) path (optional) — exact file path
Examples: obsidian_backlinks({ file: "Project Plan" }) obsidian_backlinks({ path: "Ideas/brainstorm.md" })
Inputs: file, path.
obsidian_commandA
Execute an Obsidian command by its canonical command ID.
Wraps the CLI's command Verb. Triggers any core or plugin command exactly as the user would from the command palette — identified by its stable command ID (e.g. 'editor:toggle-bold', 'app:go-back', 'daily-notes').
Discovering IDs: run the generic obsidian tool with the commands verb to list every available command ID, or commands filter=<prefix> to narrow by prefix (e.g. 'commands filter=editor:').
Parameters: id (required) — the command ID to execute
Examples: obsidian_command({ id: "editor:toggle-bold" }) obsidian_command({ id: "daily-notes" })
Inputs: id (required).
obsidian_createA
Create a new PLAIN note (no Templater expansion).
This wraps the CLI's create verb. It does NOT expand Templater placeholders
like <% tp.date.now() %> — if your template contains placeholders, use
obsidian_create_from_template instead, which routes to
templater:create-from-template.
Parameters: name (optional) — file name for the new note path (optional) — vault-relative path content (optional) — initial markdown content (literal, no placeholder expansion)
Examples: obsidian_create({ name: "Meeting 2026-04-03", content: "# Meeting Notes\n\n- Attendees: ..." }) obsidian_create({ path: "Projects/new-idea.md", content: "# New idea" })
Inputs: name, path, content.
obsidian_create_from_templateA
Create a new note from a Templater template, expanding placeholders.
This wraps the CLI's templater:create-from-template verb. Use this whenever
the template contains Templater placeholders such as <% tp.date.now() %>,
<% tp.file.title %>, or any other <% ... %> expression — those are
evaluated by Obsidian's Templater plugin and substituted into the output.
For plain notes with no placeholder expansion, use obsidian_create.
Parameters: template (required) — vault-relative path to the Templater template (e.g. "Templates/daily.md") file (required) — vault-relative output path for the new note (e.g. "Daily/2026-05-18.md")
Examples: obsidian_create_from_template({ template: "Templates/daily.md", file: "Daily/2026-05-18.md" }) obsidian_create_from_template({ template: "Templates/project.md", file: "Projects/new-idea.md" })
Inputs: file (required), template (required).
obsidian_daily_appendA
Append content to today's daily note.
Parameters: content (required) — markdown text to append at the end of today's daily note
Examples: obsidian_daily_append({ content: "- Meeting with team at 3pm" }) obsidian_daily_append({ content: "> [!tip] Remember\n> Review PR before EOD" })
Inputs: content (required).
obsidian_daily_pathA
Get the file path of today's daily note.
Returns the vault-relative path (e.g. 'Daily/2026-04-03.md'). Useful for constructing paths for other tools.
Inputs: no named parameters.
obsidian_daily_readA
Read today's daily note contents.
Returns the full markdown content of today's daily note. Returns an error if no daily note exists for today.
Inputs: no named parameters.
obsidian_deleteA
Delete a note, selecting it by file name or exact path.
Wraps the CLI's delete Verb. DESTRUCTIVE: by default the note is moved to the system trash (recoverable). Pass permanent: true to skip the trash and delete irrecoverably — there is no undo for a permanent delete.
Parameters: file (optional) — note name using wikilink resolution (e.g. 'My Note') path (optional) — exact vault-relative path (e.g. 'folder/My Note.md') permanent (optional) — true to skip trash and delete permanently (irreversible) One of file or path is required.
Examples: obsidian_delete({ file: "Old Draft" }) — moves to trash obsidian_delete({ path: "Inbox/spam.md", permanent: true }) — irreversible
Inputs: file, path, permanent.
obsidian_filesA
List files in the vault or a specific folder.
Parameters: folder (optional) — filter by folder path ext (optional) — filter by file extension (e.g. 'md', 'canvas')
Examples: obsidian_files({}) obsidian_files({ folder: "Projects/", ext: "md" })
Inputs: ext, folder.
obsidian_helpA
Get Obsidian help: a live verb index from the CLI, or reference docs by slug.
Parameters: topic (optional) — a verb name (e.g. "read", "daily:append", "property:set") OR a reference-doc slug (cli, markdown, bases, canvas)
Behavior:
No topic — returns the live, category-grouped verb index parsed from the CLI's
helpoutput (Read, Write, Edit, Discover, Tasks, Daily, Properties, Plugins, Dev, Eval).Verb name — returns that verb's description and flag list from the live manifest.
Doc slug — returns the Kepano-derived reference prompt (markdown / bases / canvas / cli syntax).
Collision rule: the four reserved doc slugs (cli, markdown, bases, canvas) always return their reference doc, even when a CLI verb shares the name (e.g.
bases). The shadowed verb still appears in the no-arg verb index.
Examples:
obsidian_help({}) — browse the verb catalog
obsidian_help({ topic: "read" }) — live verb help for read
obsidian_help({ topic: "markdown" }) — Obsidian-flavored markdown reference
obsidian_help({ topic: "bases" }) — Bases YAML schema, filters, formulas
obsidian_help({ topic: "canvas" }) — JSON Canvas reference
obsidian_help({ topic: "cli" }) — CLI command syntax reference
Inputs: topic.
obsidian_historyA
List the saved file-history versions of a note, selecting it by file name or exact path.
Wraps the CLI's history Verb. Returns the version history (snapshots/sync revisions) recorded for a single note — not a list of recently-modified notes. Provide one of file or path to select the note.
Parameters: file (optional) — note name using wikilink resolution (e.g. 'My Note') path (optional) — exact vault-relative path (e.g. 'folder/My Note.md') One of file or path is required.
Examples: obsidian_history({ file: "Project Plan" }) obsidian_history({ path: "Daily/2026-05-20.md" })
Inputs: file, path.
obsidian_moveA
Move or rename a note, selecting it by file name or exact path.
Wraps the CLI's move Verb. Provide one of file or path to select the note, and to for the destination. Setting to to a new name in the same folder renames the note.
Parameters: file (optional) — note name using wikilink resolution (e.g. 'My Note') path (optional) — exact vault-relative path (e.g. 'folder/My Note.md') to (required) — destination folder or vault-relative path One of file or path is required.
Examples: obsidian_move({ file: "My Note", to: "Archive/" }) obsidian_move({ path: "Inbox/idea.md", to: "Projects/idea.md" })
Inputs: to (required), file, path.
obsidian_outlineA
List the heading outline of a note, selecting it by file name or exact path.
Wraps the CLI's outline Verb. Provide one of file or path. Optional format controls the output shape; optional total returns just the heading count.
Parameters: file (optional) — note name using wikilink resolution (e.g. 'My Note') path (optional) — exact vault-relative path (e.g. 'folder/My Note.md') format (optional) — output format: 'tree' (default), 'md', or 'json' total (optional) — true to return the heading count instead of the outline One of file or path is required.
Examples: obsidian_outline({ file: "Meeting Notes" }) obsidian_outline({ path: "Projects/plan.md", format: "json" }) obsidian_outline({ file: "Long Doc", total: true })
Inputs: file, path, total, format.
obsidian_propertiesA
List or read frontmatter properties.
Parameters: file (optional) — note name for wikilink resolution path (optional) — exact file path name (optional) — specific property name to read (requires file or path)
Examples: obsidian_properties({}) — list all properties with counts obsidian_properties({ file: "My Note" }) — properties of a specific note obsidian_properties({ file: "My Note", name: "status" }) — read one property
Inputs: file, name, path.
obsidian_property_setA
Set a frontmatter property on a note.
Parameters: name (required) — property name value (required) — property value (see type for multi-valued props) type (optional) — property type: text (default) | list | number | checkbox | date | datetime file (optional) — note name (wikilink resolution) path (optional) — exact file path One of file or path is required.
Multi-valued properties (tags, aliases, Links, etc.): You MUST pass type="list" AND a JSON-array string as value. Without type="list" the value is written as a single scalar string — a comma-separated value is NOT split into YAML list items, and bracketed wikilinks are never split. Use a JSON array universally; it is unambiguous for both plain strings and wikilinks.
Examples: obsidian_property_set({ name: "status", value: "done", file: "My Task" }) obsidian_property_set({ name: "tags", value: "["project", "active"]", type: "list", path: "Work/todo.md" }) obsidian_property_set({ name: "Links", value: "["[[plan]]", "[[baseline]]"]", type: "list", file: "My Task" })
Inputs: name (required), value (required), file, path, +1 more.
obsidian_readA
Read a note by file name (wikilink-style) or exact path.
Parameters: file (optional) — note name using wikilink resolution (e.g. 'My Note') path (optional) — exact vault-relative path (e.g. 'folder/My Note.md') One of file or path is required.
Examples: obsidian_read({ file: "Meeting Notes" }) obsidian_read({ path: "Projects/todo.md" })
Inputs: file, path.
obsidian_recentsA
List recently opened files.
Returns the most recently opened files in the vault, ordered by last access time.
Inputs: no named parameters.
obsidian_renameA
Rename a note, selecting it by file name or exact path.
Wraps the CLI's rename Verb. Provide one of file or path to select the note, and name for the new file name. Renaming changes only the name within the same folder; use obsidian_move to relocate a note to a different folder.
Parameters: file (optional) — note name using wikilink resolution (e.g. 'My Note') path (optional) — exact vault-relative path (e.g. 'folder/My Note.md') name (required) — the new file name One of file or path is required.
Examples: obsidian_rename({ file: "Draft", name: "Final" }) obsidian_rename({ path: "Inbox/idea.md", name: "refined-idea.md" })
Inputs: name (required), file, path.
obsidian_searchA
Full-text search across the vault with line context.
Parameters: query (required) — search terms, supports Obsidian query syntax path (optional) — restrict results to a folder path limit (optional) — max number of files to return
Examples: obsidian_search({ query: "meeting notes" }) obsidian_search({ query: "project status", path: "Work/", limit: 5 })
Inputs: query (required), path, limit.
obsidian_tagsA
List tags in the vault with counts.
Returns structured JSON content (an array of { tag, count } objects) alongside the text form, so clients can consume it without re-parsing.
Parameters: sort (optional) — 'name' or 'count' (default: name)
Examples: obsidian_tags({}) obsidian_tags({ sort: "count" })
Inputs: sort.
obsidian_tasksA
List tasks from vault notes.
Returns structured JSON content (an array of task objects with status, text, file, and line) alongside the text form, so clients can consume it without re-parsing.
Parameters: daily (optional) — true to show only today's daily note tasks todo (optional) — true to show only incomplete tasks done (optional) — true to show only completed tasks path (optional) — filter by file path
Examples: obsidian_tasks({ daily: true }) obsidian_tasks({ todo: true, path: "Projects/" })
Inputs: done, path, todo, daily.
obsidian_template_readA
Read the content of a template by name from the vault's templates folder.
Wraps the CLI's template:read Verb. Returns the raw template text. Set resolve to expand the template's variables (e.g. Templater placeholders) instead of returning them literally; pass title to supply the title used during that variable resolution.
Parameters: name (required) — template name (as it appears in the templates folder) resolve (optional) — true to resolve/expand template variables title (optional) — title used for variable resolution (with resolve)
Examples: obsidian_template_read({ name: "daily" }) obsidian_template_read({ name: "meeting", resolve: true, title: "Standup 2026-05-20" })
Inputs: name (required), title, resolve.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Most tools have clearly distinct purposes (read, search, create, delete, etc.), and the descriptions are detailed enough to avoid confusion. The main overlap is between obsidian_move and obsidian_rename (move can also rename), and the generic obsidian tool intentionally overlaps with all convenience tools, but the cheatsheet and tool descriptions clarify when to use each.
Tool names consistently use the obsidian_ prefix and snake_case, which is predictable. However, the bare 'obsidian' tool breaks the pattern, and naming styles mix verbs (read, search, create) and nouns (tags, files, history), creating minor inconsistency.
At 23 tools, this fits the 16-25 'borderline heavy' range. Each tool wraps a distinct CLI verb and earns its place, but the set feels bloated, especially with the generic obsidian tool that can already perform any command.
The surface covers a wide range of Obsidian operations: CRUD for notes, daily notes, templates, properties, tags, tasks, search, backlinks, history, and outline. Minor gaps exist: there is no convenience tool for editing a note's content (only property_set and daily_append), but the generic obsidian tool can handle this via CLI commands.
Maintenance
Related MCP Connectors
Search your Obsidian vault to quickly find notes by title or keyword, summarize related content, a…
Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.
Share context and questions between Claude instances — VS Code, claude.ai web, and mobile.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConnects Claude.ai to your local Obsidian vault for full CRUD access, search, and daily note creation via the Model Context Protocol.14MIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude Desktop to your Obsidian vault, enabling reading, writing, searching, and organizing notes locally.1MIT
- FlicenseNot gradedqualityDmaintenanceLets Claude save conversations, notes, and structured summaries directly to your Obsidian vault. Supports YAML frontmatter, auto-backlinks, daily notes, and vault search.-
- AlicenseAqualityDmaintenanceEnables interaction with Obsidian vaults through the official Obsidian CLI, allowing note management, search, and vault operations without plugins or API keys.21MIT