Obsidian Local REST API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_directoryA | List directory contents with pagination to prevent context overflow. Shows immediate contents by default. |
| read_fileB | Read content of a specific file from the vault |
| write_fileC | Write file content with different modes: overwrite (default), append, or prepend. Handles both create and update operations. |
| delete_itemC | Delete a file or directory from the vault |
| create_or_update_noteA | Create or update a note with content and frontmatter. Performs upsert operation - creates if doesn't exist, updates if it does. |
| get_daily_noteA | Get daily note for a specific date. Handles common daily note naming conventions and file locations. |
| get_recent_notesC | Get recently modified notes, ordered by modification time |
| search_vaultC | Search vault content across files, filenames, and metadata with advanced filtering |
| find_related_notesB | Find notes related to a given note based on shared tags, links, or backlinks |
| get_noteC | Get a specific note with its content and metadata (legacy) |
| list_notesB | List all notes in the vault with optional search filter (legacy with search support) |
| get_metadata_keysB | Get all available frontmatter keys from notes |
| get_metadata_valuesC | Get all unique values for a specific frontmatter key |
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 13 tools
Most tools have distinct purposes, but there is some overlap between get_note/read_file and create_or_update_note/write_file that could cause confusion. The descriptions help clarify differences (e.g., get_note is legacy, write_file handles append/prepend modes), but an agent might still misselect between these pairs in certain scenarios.
All tool names follow a consistent verb_noun pattern with snake_case throughout (e.g., create_or_update_note, list_directory, search_vault). There are no deviations in naming conventions, making the set predictable and easy to parse.
With 13 tools, this server is well-scoped for managing an Obsidian vault, covering operations like CRUD for notes/files, metadata handling, search, and directory listing. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides comprehensive coverage for vault management, including create, read, update, delete, search, and metadata operations. A minor gap exists in note linking or backlink management beyond find_related_notes, but core workflows are well-supported with no dead ends.