obsidian-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_HOST | No | Host of the Windows machine running Obsidian. Leave empty for automatic IP detection in WSL2. | |
| OBSIDIAN_PORT | No | Port used by the Obsidian Local REST API plugin. | 27124 |
| OBSIDIAN_API_KEY | Yes | API key generated by the Obsidian Local REST API plugin. | |
| OBSIDIAN_PROTOCOL | No | Protocol used to connect to the Obsidian Local REST API plugin. | https |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_active_fileA | Retorna o caminho e conteúdo completo da nota atualmente aberta ou em foco na janela do Obsidian no Windows. |
| open_fileA | Abre uma nota na interface do Obsidian no Windows, tornando-a a aba ativa. |
| read_noteB | Lê o conteúdo markdown completo de uma nota do vault do Obsidian. |
| create_or_update_noteB | Cria uma nova nota ou sobrescreve o conteúdo de uma nota existente no vault do Obsidian. |
| append_to_noteC | Adiciona texto ao final de uma nota existente no vault do Obsidian. |
| delete_noteC | Exclui uma nota do vault do Obsidian. |
| list_filesB | Lista arquivos e subpastas de um diretório do vault do Obsidian. |
| search_notesC | Pesquisa notas no vault utilizando o índice interno de busca do Obsidian. |
| list_tagsA | Lista todas as tags utilizadas no vault e a quantidade de ocorrências de cada uma. |
| list_commandsB | Lista todos os comandos da paleta do Obsidian disponíveis no Windows. |
| execute_commandC | Executa uma ação da paleta de comandos do Obsidian no Windows. |
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 11 tools
Most tools target a distinct resource+action (read_note, delete_note, list_tags, execute_command). The main overlap is between get_active_file and read_note, which both return note content, though the 'active/focused' scope distinguishes them; create_or_update_note also bundles two actions but is unambiguous.
All 11 tools follow a consistent snake_case verb_noun pattern (get_active_file, open_file, read_note, append_to_note, list_files, search_notes). No mixing of camelCase or alternate verb styles.
11 tools is well within the ideal 3-15 range for a vault/note management server. Each tool earns its place covering file navigation, CRUD, search, tags, and command execution without redundancy.
Core lifecycle is covered: read, create/update, append, delete, plus listing, search, tags, and command execution. Minor gaps exist (no rename/move note, no folder creation, no metadata/frontmatter access), but agents can work around these using create_or_update_note and execute_command.