live-mcp-for-obsidian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| vault | No | Target a specific vault by name (CLI flag --vault or -v) | |
| obsidian_path | No | Path to the Obsidian binary (CLI flag --obsidian-path) | /Applications/Obsidian.app/Contents/MacOS/Obsidian |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| obsidian_statusA | Get Obsidian version, vault name, path, file/folder counts, and size |
| obsidian_vaultsA | List all known vaults |
| obsidian_tabsA | List open tabs in the main editor area. Use 'all' to include sidebar panels. |
| obsidian_workspaceB | Show the workspace tree layout |
| obsidian_openC | Open a file in Obsidian |
| obsidian_filesA | List files in the vault, optionally filtered by folder or extension |
| obsidian_readB | Read the contents of a file |
| obsidian_createB | Create a new file in the vault |
| obsidian_appendB | Append content to a file |
| obsidian_prependC | Prepend content to a file |
| obsidian_deleteA | Delete a file (moves to trash by default) |
| obsidian_moveB | Move or rename a file |
| obsidian_searchB | Search files, tags, properties, or links in the vault |
| obsidian_pluginsA | List installed plugins with enabled/disabled state |
| obsidian_plugin_infoA | Get detailed info about a specific plugin |
| obsidian_plugin_enableC | Enable a plugin |
| obsidian_plugin_disableB | Disable a plugin |
| obsidian_plugin_reloadA | Reload a plugin (useful during development) |
| obsidian_commandsA | List available Obsidian commands, optionally filtered by prefix |
| obsidian_commandB | Execute an Obsidian command by ID |
| obsidian_themeA | Show active theme info or get details about a specific theme |
| obsidian_themesC | List installed themes |
| obsidian_snippetsA | List installed CSS snippets |
| obsidian_propertiesB | List properties in the vault or for a specific file |
| obsidian_property_setC | Set a property on a file |
| obsidian_tagsA | List tags in the vault or for a specific file |
| obsidian_linksA | List outgoing links from a file |
| obsidian_backlinksA | List backlinks to a file |
| obsidian_outlineA | Show headings for a file |
| obsidian_tasksB | List tasks in the vault or a specific file |
| obsidian_dailyC | Open or read the daily note |
| obsidian_daily_appendB | Append content to the daily note |
| obsidian_evalC | Execute JavaScript in Obsidian and return the result |
| obsidian_domA | Query DOM elements by CSS selector |
| obsidian_consoleB | Show captured console messages from Obsidian |
| obsidian_errorsC | Show captured errors from Obsidian |
| obsidian_screenshotA | Take a screenshot of Obsidian. Uses Chrome DevTools Protocol for full-window or element-targeted captures. |
| obsidian_cssB | Inspect CSS with source locations for a selector |
| obsidian_cdpC | Run a Chrome DevTools Protocol command directly |
| obsidian_debugC | Attach or detach the Chrome DevTools Protocol debugger |
| obsidian_mobileC | Toggle mobile emulation on or off |
| obsidian_devtoolsA | Toggle Electron DevTools open/closed |
| obsidian_briefingA | Get a snapshot of the current Obsidian state: active file, open tabs, daily note, recent files, vault stats, and CLAUDE.md instructions if present. Call this at the start of a session for instant context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 43 tools
Most tools have distinct purposes, but there is potential confusion among similar-sounding ones like obsidian_links vs obsidian_backlinks vs obsidian_outline vs obsidian_properties. However, descriptions are clear enough to distinguish them.
All tools follow the 'obsidian_' prefix consistently, and the naming pattern (verb or noun) is uniform, with no mixing of conventions.
With 43 tools, the set is significantly larger than the typical 3-15 range considered appropriate. Many tools are for debugging and development, which expands the scope beyond core note-taking functionality.
The tool set covers nearly all aspects of Obsidian interaction: file operations, metadata, plugins, themes, search, daily notes, vault management, and developer tools. There are no obvious gaps for common use cases.