obx
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_PATH | Yes | The absolute or relative path to the Obsidian vault to be accessed by the server. | |
| OBSIDIAN_ADDR | No | Environment variable or flag (--http) to run as an HTTP server on the specified address (e.g., :8080). | |
| ALLOWED_VAULTS | No | Comma-separated list of vault aliases defined via 'obx vault add' that the agent is permitted to switch to. | |
| DISABLED_TOOLS | No | Comma-separated list of tool groups to blacklist (e.g., 'manage-folders,bulk-operations'). | |
| ALLOW_VAULT_SWITCHING | No | Whether to allow the AI assistant to switch the active vault dynamically via the MCP protocol. |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze-vaultB | Unified analytical tool to get vault stats, detect broken links, orphans, stubs, and outdated notes |
| bulk-operationsB | Unified bulk operational tool for tagging, moving, and updating frontmatter across multiple notes |
| edit-noteB | Unified tool for targeted text edits, section replacements, and batch edits |
| manage-canvasC | Unified tool for reading, creating, and interacting with Canvas notes |
| manage-foldersB | Unified tool for listing, creating, and deleting folders |
| manage-frontmatterB | Unified tool for manipulating note frontmatter properties, tags, aliases, and inline fields |
| manage-linksB | Unified tool covering backlinks, forward-links, and AI link suggestions for notes |
| manage-mocsC | Unified tool to discover and generate Maps of Content (MOCs) and folder indices |
| manage-notesC | Unified tool for listing, reading, writing, moving, deleting, renaming, and appending to notes |
| manage-periodic-notesB | Unified tool for getting, creating, and listing daily, weekly, monthly, and yearly periodic notes |
| manage-tasksB | Unified tool for finding, toggling, and completing checkbox tasks across the vault |
| manage-templatesA | Unified tool for listing, retrieving, and applying markdown templates |
| read-batchB | Unified tool for reading batches of notes, specific headings, sections, or generated summaries |
| refactor-notesA | Unified tool for structural note refactoring: split notes by heading, merge multiple notes, and extract sections to new notes |
| search-vaultB | Unified search tool spanning text query, advanced block search, regex, dates, tags, inline-fields, and frontmatter queries |
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
Each tool has a clearly distinct domain (e.g., analytics, bulk ops, editing, canvas, folders, frontmatter, links, MOCs, notes, periodic notes, tasks, templates, batch reading, refactoring, search). No two tools appear to have overlapping purposes; descriptions clarify unique responsibilities.
Most tools use a verb-noun pattern with hyphens, but the verbs are inconsistent: 'manage-', 'analyze-', 'bulk-', 'edit-', 'read-', 'refactor-', 'search-'. While readable, the lack of a uniform prefix or verb style introduces minor confusion.
With 15 tools covering the full lifecycle of vault management (reading, writing, organizing, searching, analyzing, templating), the count is well-scoped. Each tool serves a distinct purpose without being excessive or thin.
The tool surface is remarkably complete: full CRUD for notes, folders, periodic notes, templates, tasks; plus advanced features like bulk operations, refactoring, batch reading, canvas interaction, MOC generation, and search. No obvious gaps for a note-taking vault.