Obsidian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_HOST | No | Host for Obsidian Local REST API | 127.0.0.1 |
| OBSIDIAN_PORT | No | Port for Obsidian Local REST API (27124 for HTTPS, 27123 for HTTP) | 27124 |
| OBSIDIAN_SECURE | No | Whether to use HTTPS (true) or HTTP (false) | true |
| OBSIDIAN_API_KEY | Yes | Your Obsidian API key (required by Local REST API plugin) |
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_server_infoA | Get Obsidian server information and authentication status |
| update_active_fileA | Replace the content of the currently active file |
| append_to_active_fileC | Append content to the currently active file |
| get_fileC | Get the content of a specific file in the vault |
| create_or_update_fileB | Create a new file or update an existing one |
| append_to_fileB | Append content to a file (creates file if it does not exist) |
| delete_fileB | Delete a file from the vault |
| list_directoryB | List files and folders in a directory |
| search_simpleB | Perform a simple text search across the vault |
| get_commandsA | Get a list of available Obsidian commands |
| execute_commandC | Execute an Obsidian command |
| open_fileC | Open a file in the Obsidian interface |
| get_periodic_noteA | Get current periodic note for the specified period |
| append_to_periodic_noteC | Append content to current periodic note |
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 14 tools
Most tools have clearly distinct purposes, but there is potential confusion between active-file operations (update_active_file, append_to_active_file) and general file operations (create_or_update_file, append_to_file). Descriptions clarify the distinction, but the overlap in functionality could cause an agent to select the wrong tool in some contexts.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_file, create_or_update_file, delete_file). The naming is uniform with no style mixing, and the verbs clearly indicate the action being performed.
With 14 tools, the server covers the core of Obsidian's note-taking functionality without becoming overwhelming. Each tool serves a distinct purpose, and the count is well within the typical range for a domain-specific MCP server.
The tool set covers CRUD operations for files, search, directory listing, command execution, and periodic notes—covering the main workflows. However, there are minor gaps: no way to read the currently active file (only update/append it), and no rename/move or folder creation operations. These are workable but not ideal.