obsidian-agi-workspace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind host for SSE/HTTP server | 0.0.0.0 |
| PORT | No | Port for SSE/HTTP server | 8080 |
| OB_BIN_PATH | No | Custom binary path for Obsidian Headless CLI | ob |
| MCP_TRANSPORT | No | Transport protocol: 'stdio' (CLI) or 'sse' / 'http' (Server) | stdio |
| OBSIDIAN_READONLY | No | When 'true', rejects note creation, edits, and deletions | false |
| OBSIDIAN_VAULT_PATH | Yes | Absolute filesystem path to the Obsidian vault root | |
| OBSIDIAN_ALLOWED_SUBPATHS | No | Comma-separated list of permitted relative subfolders (if not set, full vault is accessible) |
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_folderB | Create a new folder or directory hierarchy inside the Obsidian vault. |
| list_foldersB | List folders and directory structure in the vault with note counts. |
| get_vault_treeA | Retrieve hierarchical directory tree of folders and notes in the vault for workspace overview. |
| read_noteA | Read an Obsidian note with frontmatter, body, metadata, wikilinks, and backlinks. |
| write_noteA | Create or overwrite a note in the Obsidian vault with structured YAML frontmatter and body. |
| patch_noteA | Perform fine-grained updates on an existing Obsidian note (append, prepend, replace under heading, regex patch, update frontmatter). |
| search_vaultA | Search vault notes by keyword, tags, frontmatter filters, or directory subpath. |
| list_tasksA | Aggregate markdown task checkboxes (- [ ] / - [x]) across the Obsidian vault. |
| analyze_workspace_graphA | Analyze knowledge graph topology: nodes, wikilink edges, orphan notes, and dangling (broken) links. |
| sync_vault_obB | Trigger an immediate Obsidian Sync cycle or inspect synchronization state via obsidian-headless ( |
| delete_itemA | Safely delete a note or folder (moves to .trash by default). |
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 have clear boundaries: note operations (read/write/patch), folder operations (create/list/delete), and analysis (search/tasks/graph/sync) are distinct. Minor overlap exists between list_folders and get_vault_tree, but their descriptions (note counts vs. hierarchical tree) differentiate them enough.
The dominant pattern is verb_noun (create_folder, read_note, patch_note, search_vault). Exceptions are delete_item, which is generically named instead of delete_note_or_folder, and sync_vault_ob, where the '_ob' suffix is opaque and inconsistent with the rest of the API.
11 tools is well-scoped for an Obsidian workspace server. Each tool addresses a concrete operational need without excessive redundancy, and the count feels appropriate for the feature set.
The surface covers core workspace operations well: folder creation, note CRUD, search, task aggregation, graph analysis, sync, and deletion. Obvious gaps are rename/move operations for notes or folders, which would make the lifecycle more complete, but agents can generally work around this.