obsidian-connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT_PATH | Yes | Absolute path to the vault folder | |
| OBSIDIAN_DAILY_FOLDER | No | Vault-relative folder for daily notes (default: root) | |
| OBSIDIAN_DAILY_FORMAT | No | Daily-note filename format using YYYY/MM/DD (default: YYYY-MM-DD) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesA | List Markdown notes in the vault, optionally limited to a sub-folder. |
| list_foldersA | List immediate sub-folders of the vault or a given folder. |
| read_noteA | Read a note. Optionally return only a single heading's section, or a line range, to save tokens on large notes. |
| get_note_infoA | Return metadata for a note (created/modified time, size, tags, frontmatter keys, outgoing link and task counts) without its full body. |
| search_notesA | Search the vault by text or regular expression, optionally filtered by tag and path glob. Returns matching notes with snippets. |
| list_tagsA | List every tag used in the vault with the number of notes using each. |
| get_backlinksA | Find notes that link to the target note via [[wikilinks]] (matched on file name). |
| get_outgoing_linksA | List the [[wikilinks]] and ![[embeds]] a note points to, marking which targets exist in the vault. |
| list_tasksA | List Markdown task checkboxes ( |
| create_noteA | Create a new note with optional YAML frontmatter. Fails if it exists unless 'overwrite' is true. |
| append_to_noteA | Append text to a note, optionally under a specific heading. Creates the note if missing. |
| edit_noteA | Edit an existing note: either find/replace text, or replace the entire body under a heading. Use 'find'+'replace' for text edits, or 'section'+'replace' to rewrite a heading's content. |
| update_frontmatterA | Set or remove YAML frontmatter fields on an existing note without touching its body. |
| toggle_taskA | Toggle a Markdown task checkbox on a given line (use list_tasks to find the line number). |
| move_noteA | Move or rename a note and rewrite [[wikilinks]] in other notes that point to it. Refuses to overwrite an existing file unless 'overwrite' is true. |
| delete_noteA | Move a note to the vault's .trash folder (recoverable; not a permanent delete). |
| append_to_daily_noteA | Append an entry to today's (or a given date's) daily note, creating it with a heading if missing. Folder/format come from settings. |
| append_to_periodic_noteA | Append an entry to a daily, weekly or monthly note (created with a heading if missing). Folder/format per period come from settings. |
| read_periodic_noteA | Read the daily, weekly or monthly note for today or a given date. |
| create_note_from_templateA | Create a note from a template file, substituting {{title}}, {{date}}, {{time}} and any custom {{variables}}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_note | Read a note and produce a concise summary with key points and any action items. |
| daily_review | Review today's daily note and surface open tasks across the vault. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| vault-structure | An overview of the vault: top-level folders and a count of notes. |
TDQS
Scored across 20 tools
Each tool has a distinct purpose. While there are several 'append' and 'list' tools, they target different entities (daily note, periodic note, tasks, tags, etc.) and are clearly differentiated by name and description.
All tool names use consistent verb_noun snake_case pattern (e.g., append_to_note, create_note, list_tasks, read_note). The verb choice is appropriate and uniform across the set.
20 tools is on the higher side but each tool addresses a specific need in Obsidian interaction (CRUD notes, tasks, tags, links, folders, search, frontmatter). The set is comprehensive without being bloated.
Covers all core operations: creating, reading, editing, deleting, moving notes; managing tasks; searching; frontmatter; backlinks/outgoing links; periodic notes; tags; folders. Only minor attachments or graph operations are missing, which are niche.