hebbian-vault
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEBBIAN_VAULT_LICENSE | No | Pro license JWT (also accepted via --license-key flag) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| configure_vaultA | Configure the vault path for this server. Call this first if the server started without a --vault argument. The vault_path must be an absolute path to an Obsidian vault directory containing .md files. |
| vault_searchA | Search the vault with hybrid ranking. Results are ranked by keyword relevance, graph centrality, and usage frequency merged via Reciprocal Rank Fusion. Each returned result strengthens that file's future ranking (Hebbian learning). |
| vault_readA | Read a single vault note by relative path. Returns full content with parsed frontmatter, outgoing links, and incoming links. Strengthens the file's Hebbian score. |
| vault_neighborsB | Find notes connected to a given note by wikilinks. Shows both outgoing and incoming links, with PageRank scores for prioritization. |
| vault_hotA | Top-N most-used files by Hebbian score (usage frequency weighted by recency). Shows what the vault considers most important based on actual usage patterns. |
| vault_statsA | Vault-level analytics: file count, link count, orphans, broken links, average connectivity, and top hub pages by PageRank. |
| vault_healthA | Structural integrity check: broken links, orphaned leaves, missing frontmatter. Returns a list of issues found. |
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 7 tools
Each tool has a clearly distinct purpose: setup, search, read, graph navigation, hot files, stats, health. No overlapping functionality.
Most tools follow a 'vault_' prefix pattern, but 'configure_vault' breaks the pattern by placing 'vault' at the end, introducing minor inconsistency.
With 7 tools, the server covers essential operations for analyzing an Obsidian vault without unnecessary bloat or gaps.
The tool set provides strong read/analysis capabilities but lacks write operations (create, update, delete notes), which limits full vault interaction.