Obsidian 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_vaultsB | List available Obsidian vaults |
| get_vault_infoC | Get information about a specific vault |
| read_noteC | Read a note from the vault |
| write_noteC | Create or update a note in the vault |
| list_notesC | List all notes in a vault or folder |
| search_vaultC | Search for text across all notes in vault |
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 6 tools
Every tool has a clearly distinct purpose with no ambiguity. get_vault_info retrieves vault metadata, list_notes enumerates notes, list_vaults shows available vaults, read_note accesses note content, search_vault performs text searches, and write_note handles creation/updates. The boundaries are well-defined and non-overlapping.
All tools follow a consistent verb_noun pattern using snake_case. The verbs (get, list, read, search, write) are appropriately chosen for their actions, and the nouns (vault_info, notes, vaults, note, vault) clearly indicate the target resources. There are no deviations in naming conventions.
With 6 tools, this server is well-scoped for managing Obsidian vaults and notes. Each tool earns its place by covering essential operations: discovery (list_vaults, list_notes), reading (read_note, get_vault_info), writing (write_note), and searching (search_vault). The count is neither too sparse nor bloated.
The tool surface provides strong coverage for core note-taking workflows, including CRUD operations (create/update via write_note, read via read_note, list via list_notes) and search functionality. A minor gap is the lack of a delete_note tool, which agents might need to work around, but the essentials are well-covered for the domain.