What problem does it solve?
The connected obsidian MCP server exposes only a subset of the Obsidian Local REST API, so operations like renaming a note, atomically overwriting a file, acting on the currently open note, running Obsidian commands, or listing vault tags have no MCP tool and would otherwise require fragile workarounds like delete-and-recreate.
Core Features & Use Cases
- Full REST API coverage: Exposes every endpoint of the Obsidian Local REST API, including the custom MOVE method for renaming/moving notes while preserving history and updating internal links.
- Authenticated wrapper script: The
scripts/olrapi.sh wrapper resolves host, port, and API key from ~/.claude.json or OBSIDIAN_* environment variables and handles the plugin's self-signed TLS certificate.
- Complete endpoint reference:
references/api_reference.md documents all 16 paths, header enums (Operation, Target-Type, Target-Scope), search formats (JsonLogic/Dataview), and periodic-note CRUD.
- Use Case: Rename
3-Resources/Draft.md to 3-Resources/Final.md with a single MOVE call that returns HTTP 204, preserving file history and updating internal links instead of deleting and recreating the note.
Quick Start
Ask the assistant to rename a note in your Obsidian vault using the obsidian-rest-api skill's MOVE endpoint, for example moving "Inbox/todo.md" into the "Archive/" folder.