Secure MCP server for Obsidian vaults — full file modification, atomic frontmatter ops, hardened path sandbox
Server has 22 tools with mostly present descriptions and basic schemas. Naming follows verb_noun convention well (read_note, create_note, search_notes). However, parameter descriptions are sparse or missing in many tools, only read_note and list_notes show explicit parameter descriptions in visible code. Output schemas are not documented. Error handling is present but recovery guidance is minimal. Tool composition is sound (single responsibility), but schema completeness and parameter documentation fall short of production baseline (94% of A+ tools have full param descriptions; this server ~40%).
Append content to an existing note
Create a new note in the vault
Delete a frontmatter field
Delete a note from the vault
Execute a command via the Obsidian Local REST API
Read a note's frontmatter metadata
Get metadata about the vault
Output schemas not documented. Tools return results but LLMs cannot see what fields to expect, forcing them to infer structure and plan downstream calls blindly.
Parameter descriptions missing or minimal for most tools. Only read_note and list_notes show explicit parameter descriptions in visible code. 18 of 22 tools lack documented parameter intent.
Destructive tools (delete_note, execute_command) lack explicit recovery guidance in error responses. Agents cannot determine if a failure is retryable or fatal.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | <=2025-11-25 | v2 |
List markdown notes in the vault, optionally filtered by folder.
List notes that are stale according to refresh contracts
List the capabilities of all available tools
Add or remove tags from a note's frontmatter
Merge frontmatter fields into a note
Move a note to a different folder
Apply a patch to a note's content
Read multiple notes in a single call
Read a note's full text content from the vault.
Apply a refresh update to a note with validation
Rename a note
Resolve a wikilink to its target note path
Search notes by content or metadata
Set a single frontmatter field
Update an existing note's content
execute_command tool is overly broad and dangerous. Accepts arbitrary Obsidian REST API commands with minimal validation. No rate limiting, no per-command permission gates, no dry-run support.
No pagination parameters visible for list_notes and search_notes. Large vaults could return thousands of results, exhausting context window. Baseline expects limit + offset/cursor.