obsidian-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_API_KEY | Yes | Your Obsidian Local REST API key | |
| OBSIDIAN_BASE_URL | No | Base URL of the Obsidian Local REST API | https://127.0.0.1:27124 |
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 |
|---|---|
| obsidian_statusA | Check whether Obsidian Local REST API is reachable and authenticated. |
| obsidian_listA | List files and folders at a vault directory (root when path is omitted). |
| obsidian_readA | Read a note as markdown, or as structured JSON metadata when asJson is true. |
| obsidian_createA | Create a note or replace its entire contents. |
| obsidian_appendA | Append markdown to the end of a note (creates the note if needed). |
| obsidian_deleteA | Delete a note. By default moves to trash; set permanent=true only when the user explicitly asks. |
| obsidian_patchB | Insert, prepend, or replace content relative to a heading, block reference, or frontmatter field. |
| obsidian_searchB | Full-text search across the vault using Obsidian's simple search. |
| obsidian_daily_readA | Read today's daily note using OBSIDIAN_DAILY_NOTE_PATH (default Daily/YYYY-MM-DD.md). |
| obsidian_daily_appendA | Append markdown to today's daily note (creates it if missing). |
| obsidian_tags_listA | List all tags in the vault with usage counts. |
| obsidian_files_by_tagB | Find notes that contain a given tag via vault search. |
| obsidian_openB | Open a note in the Obsidian UI. |
| obsidian_commands_listA | List available Obsidian commands. |
| obsidian_command_executeA | Execute an Obsidian command by id. Only use when the user explicitly asks for it. |
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 15 tools
Most tools have clear distinct purposes, but the overlapping modify operations (create, append, patch) and specialized daily note variants (daily_read, daily_append) could potentially be confused by an agent without careful reading. Overall, descriptions help disambiguate.
Tool names share the 'obsidian_' prefix but mix verb-only names (create, append, read), verb-object names (daily_read, daily_append), noun-verb names (tags_list, commands_list), and a noun phrase (files_by_tag). This inconsistency makes the set less predictable.
With 15 tools, the server is well-scoped for Obsidian vault management, covering CRUD, search, tags, daily notes, commands, and UI interaction. It's slightly on the higher end but still appropriate for the breadth of functionality.
The core note lifecycle is covered (create, read, update via append/patch, delete), along with search, tags, daily notes, and command execution. Minor gaps exist such as no rename/move or folder creation, but these are not critical for most workflows.