neuro-vault-mcp 5.2.0 → 5.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -55,6 +55,7 @@ A few more questions Neuro Vault makes one-shot:
55
55
  > _"Show meeting notes from `Work/` from the last two weeks, newest first."_
56
56
  > _"Find notes similar to this one I'm reading."_
57
57
  > _"Append today's decision to the daily note."_
58
+ > _"What's on my agenda today — and what did I capture in other notes since this morning?"_
58
59
  > _"What did past-me write about retrieval policy before I started building it?"_
59
60
 
60
61
  One question, one answer. Your assistant stops being a file browser and starts being an actual second brain.
@@ -125,7 +126,7 @@ User guide lives in [`docs/guide/`](./docs/guide/README.md):
125
126
 
126
127
  - [Installation](./docs/guide/installation.md)
127
128
  - [Semantic Search](./docs/guide/semantic-search.md) — `search_notes`, `get_similar_notes`, `find_duplicates`, `get_stats`
128
- - [Vault Operations](./docs/guide/vault-operations.md) — note CRUD, daily notes, properties, tags, structured queries (`query_notes`)
129
+ - [Vault Operations](./docs/guide/vault-operations.md) — note CRUD, daily notes, properties, tags, structured queries (`query_notes`), vault snapshot (`get_vault_overview`)
129
130
  - [Routing Between Tools](./docs/guide/routing.md)
130
131
  - [Configuration](./docs/guide/configuration.md) — CLI args, troubleshooting, limitations, **migration to 2.0**, development
131
132
 
@@ -133,6 +134,12 @@ Architecture / internals: [`docs/architecture/`](./docs/architecture/).
133
134
 
134
135
  ---
135
136
 
137
+ ### Vault-specific conventions for external agents
138
+
139
+ When the server starts, it looks for `<vault>/.neuro-vault/for-external-agents.md`. If the file exists, its content is appended to the MCP `instructions` that clients receive at `initialize`, under a `## Vault-specific conventions` section. Use this file to teach external agents vault-specific rules that cannot be derived from the snapshot — for example, closed sets of frontmatter `type` values, or folders that are off-limits for writes. The file is optional; without it the server still ships sane defaults plus a pointer to `get_vault_overview`.
140
+
141
+ ---
142
+
136
143
  ## 📄 License
137
144
 
138
145
  ISC — see [LICENSE](LICENSE).
package/dist/cli.d.ts CHANGED
@@ -242,11 +242,11 @@ interface OperationsModuleDeps {
242
242
  graph?: WikilinkGraphIndex;
243
243
  }
244
244
 
245
- type ToolServer = Pick<McpServer, 'registerTool' | 'connect'>;
245
+ type ToolServer = Pick<McpServer, 'registerTool' | 'registerResource' | 'connect'>;
246
246
  interface NeuroVaultStartupDependencies {
247
247
  semantic?: SemanticModuleDeps;
248
248
  operations?: OperationsModuleDeps;
249
- serverFactory?: () => ToolServer;
249
+ serverFactory?: (instructions: string) => ToolServer;
250
250
  transportFactory?: () => StdioServerTransport;
251
251
  }
252
252