A comprehensive MCP server for Obsidian on macOS with AppleScript, URI scheme, and file system access
The server defines 20 tools with mostly adequate naming and basic schemas. However, critical gaps exist: many tool descriptions lack depth and actionable context; parameter descriptions are minimal or generic; output schemas are not documented; error handling guidance is absent; and no tool annotations (readOnlyHint/destructiveHint/idempotentHint) are present despite a mix of read, write, and destructive operations. The naming convention is solid (verb_noun prefix on all tools), but descriptions frequently fall below the 50-200 character LLM-optimized range, and descriptions for many parameters are trivial one-liners. No evidence of pagination support, result limits, or recovery guidance. The server is functional but would benefit from substantial documentation improvements before production use.
Create or open daily note in Obsidian.
Create a new note with a structured template. Args: vault: Name or path of the vault path: Path where the note should be created title: Optional title (defaults to filename) tags: Optional list of tags to add content: Optional main content body Returns: Success message or error
Delete a note from the vault. Args: vault: Name or path of the vault path: Path to the note to delete Returns: Success message or error
Bring Obsidian application to the foreground.
Get information about the currently active note in Obsidian.
Get the name of the currently active vault in Obsidian.
Get metadata about a note including tags, links, word count, and frontmatter. Args: vault: Name or path of the vault path: Path to the note within the vault Returns: JSON with note metadata
Output schemas not documented for any tool. LLMs cannot predict what fields will be returned, preventing effective composition and forcing manual exploration.
Tool annotations absent. obsidian_delete_note (DESTRUCTIVE), obsidian_move_note (REVERSIBLE), and obsidian_write_note (WRITE) lack destructiveHint/idempotentHint annotations, preventing agents from understanding side-effect severity.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | <=2025-11-25 | v2 |
Get detailed information about a specific vault. Args: vault: Name or path of the vault Returns: JSON with vault path, note count, and folder structure
Get comprehensive statistics about a vault. Args: vault: Name or path of the vault Returns: JSON with vault statistics including tag counts, link analysis
Get the version of the Obsidian application.
Check if Obsidian is currently running.
Launch Obsidian application, optionally opening a specific vault.
List all notes in a vault or specific folder. Args: vault: Name or path of the vault folder: Optional subfolder path to list (e.g., "Projects") include_attachments: Whether to include non-markdown files Returns: JSON array of note information
List all known Obsidian vaults on this Mac. Returns a JSON array of vault information including name, ID, and path.
Move or rename a note within the vault.
Open a specific note in Obsidian using URI scheme.
Read the contents of a specific note. Args: vault: Name or path of the vault path: Path to the note within the vault (e.g., "Folder/Note Name") Returns: The full content of the note as markdown text
Open search in Obsidian with optional query.
Search for notes in a vault using pattern matching.
Create a new note or overwrite an existing one. Args: vault: Name or path of the vault path: Path where the note should be created (e.g., "Folder/Note Name") content: The markdown content to write append: If true, append to existing content instead of overwriting Returns: Success message or error
Minimal parameter descriptions across many tools. obsidian_move_note, obsidian_search_notes, obsidian_search, and others provide only bare noun descriptions ('Search query string', 'Vault name or ID') without context on format, valid values, or constraints. LLMs struggle to invoke correctly.
No error handling guidance. Tools lack recovery suggestions ('If vault not found, try obsidian_list_vaults()') or error categorization (retryable vs user-fixable vs fatal). Agents cannot recover from failures.
Destructive operations (obsidian_delete_note, obsidian_write_note with overwrite) lack confirmation/dry-run patterns. Agents can permanently delete vaults or overwrite notes without verification, risking data loss.
No pagination or result limits documented. obsidian_list_notes and obsidian_list_vaults lack limit/offset/page parameters and total count returns, risking context window exhaustion on large vaults.
Ambiguous 'vault' parameter accepting both 'name or path' without guidance on which is preferred or how resolution order works. If both a vault named 'work' and a path 'work' exist, the LLM cannot predict which will be selected.
Many tool descriptions are too brief (under 50 chars). obsidian_focus ('Bring Obsidian application to the foreground.'), obsidian_is_running ('Check if Obsidian is currently running.'), obsidian_get_active_note lack context on *when* to call them and what *downstream actions* they enable.