obsidian-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT_PATH | No | Absolute path to the Obsidian vault root directory. Used as fallback if config file is not present. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_noteA | Vault 안에 새 노트를 만든다. Obsidian YAML 속성(title, aliases, tags, author, date, source, type, Service URL)이 고정 순서로 기본 부여된다. 값을 채우려면 해당 파라미터를 넘기고, 비우면 빈 키만 유지된다. |
| read_noteA | Vault 내 노트의 원문, 파싱된 frontmatter, 본문을 반환한다. |
| update_noteA | 기존 노트의 본문과 frontmatter를 수정한다. mode로 본문 갱신 방식을 정하고, 속성 파라미터를 넘기면 해당 frontmatter 키만 병합한다(나머지는 보존, 키 순서 유지). |
| list_directoryA | Vault 내 디렉토리의 파일/폴더 목록을 반환한다. (.으로 시작하는 항목 제외) |
| create_directoryA | Vault 안에 폴더를 (재귀적으로) 생성한다. |
| search_notesA | Vault 내 노트를 파일명/본문/태그 기준으로 검색한다. (대소문자 무시, 단순 부분일치) |
| get_vault_infoA | 현재 설정된 Vault 경로, 기본 author, 노트 수, config 파일 위치를 반환한다. |
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 7 tools
Each tool targets a distinct operation: create/read/update for notes, list/create for directories, search across notes, and vault info. No overlapping purposes.
All tool names follow a consistent verb_noun pattern using snake_case (create_note, read_note, update_note, list_directory, create_directory, search_notes, get_vault_info).
7 tools is well-scoped for an Obsidian vault server, covering note operations, directory management, search, and vault metadata without redundancy.
The note lifecycle covers create, read, and update but lacks delete note and delete directory operations, which are fundamental for full CRUD. Search and directory listing are present, but deletions are a notable gap.