neuro-vault-mcp 7.0.0 → 8.0.0

package/README.md

@@ -2,7 +2,7 @@
 
 > 🧠💾 **Make your personal vault usable by agents.** Low-token retrieval, explicit provenance, and safe writes for your Obsidian notes — in Claude Code, Cursor, Windsurf, and any MCP client.
 
-https://github.com/user-attachments/assets/25c1bafb-7b90-43ac-aa50-50e85705fb5b
+[https://github.com/user-attachments/assets/25c1bafb-7b90-43ac-aa50-50e85705fb5b](https://github.com/user-attachments/assets/5ac86cd7-2d67-420d-b940-dba4ae1a2ccb)
 
 [![npm version](https://img.shields.io/npm/v/neuro-vault-mcp)](https://www.npmjs.com/package/neuro-vault-mcp)
 [![Node.js](https://img.shields.io/node/v/neuro-vault-mcp)](https://nodejs.org)
@@ -140,7 +140,7 @@ Two vaults cannot share the same directory basename — the basename doubles as
 With multiple vaults registered:
 
 - **Every tool** accepts an optional `vault: "<name>"` parameter to target a specific vault.
-- **`search_notes`, `query_notes`, and `get_vault_overview`** fan out across all registered vaults when `vault` is omitted. The response shape switches to `results_by_vault: [...]` (one entry per vault) plus `skipped_vaults: [...]` for any vault the tool could not reach.
+- **`search_notes`, `query_notes`, `get_vault_overview`, `list_tags`, and `list_properties`** fan out across all registered vaults when `vault` is omitted. The response shape switches to `results_by_vault: [...]` (one entry per vault) plus `skipped_vaults: [...]` for any vault the tool could not reach and `failed_vaults: [...]` for per-vault runtime errors (`{ vault, error: { code, message, details? } }`). A single failed vault does not abort the whole call.
 - **All other tools** (writes, reads of specific paths, single-vault diagnostics) require an explicit `vault` in multi-vault mode. Omitting it returns `VAULT_REQUIRED`.
 - **Semantic fan-out** silently skips vaults whose Smart Connections `.smart-env/multi/` index is unavailable. Targeting such a vault explicitly with `vault: "<name>"` returns `SEMANTIC_INDEX_NOT_FOUND`.
 

package/dist/cli.js

@@ -14228,6 +14228,16 @@ var ToolHandlerError = class extends Error {
     }
   }
 };
+var FATAL_TOOL_ERROR_CODES = /* @__PURE__ */ new Set([
+  "INVALID_ARGUMENT",
+  "INVALID_PARAMS",
+  "INVALID_FILTER",
+  "VAULT_REQUIRED",
+  "VAULT_NOT_FOUND"
+]);
+function isFatalToolError(error48) {
+  return error48 instanceof ToolHandlerError && FATAL_TOOL_ERROR_CODES.has(error48.code);
+}
 function isPlainRecord(value) {
   return typeof value === "object" && value !== null && !Array.isArray(value) && Object.getPrototypeOf(value) === Object.prototype;
 }
@@ -15715,20 +15725,73 @@ function buildGetStatsTool(deps) {
 }
 
 // src/lib/fan-out.ts
+function findFatalRejection(settled) {
+  for (const outcome of settled) {
+    if (outcome.status === "rejected" && isFatalToolError(outcome.reason)) {
+      return outcome.reason;
+    }
+  }
+  return void 0;
+}
+function mapRejectionToFailedVault(vault, reason) {
+  if (reason instanceof ToolHandlerError) {
+    return {
+      vault,
+      error: {
+        code: reason.code,
+        message: reason.message,
+        ...reason.details ? { details: reason.details } : {}
+      }
+    };
+  }
+  return {
+    vault,
+    error: {
+      code: "INTERNAL_ERROR",
+      message: reason instanceof Error ? reason.message : String(reason)
+    }
+  };
+}
 async function runFanOut(registry2, fn) {
   const entries = registry2.list();
-  const results = await Promise.all(
-    entries.map(async (entry) => ({ vault: entry.name, ...await fn(entry) }))
-  );
-  return { results_by_vault: results, skipped_vaults: [] };
+  const settled = await Promise.allSettled(entries.map((entry) => fn(entry)));
+  const fatalError = findFatalRejection(settled);
+  if (fatalError) {
+    throw fatalError;
+  }
+  const results = [];
+  const failed = [];
+  for (let i = 0; i < settled.length; i++) {
+    const outcome = settled[i];
+    const vault = entries[i].name;
+    if (outcome.status === "fulfilled") {
+      results.push({ vault, ...outcome.value });
+    } else {
+      failed.push(mapRejectionToFailedVault(vault, outcome.reason));
+    }
+  }
+  return { results_by_vault: results, skipped_vaults: [], failed_vaults: failed };
 }
 async function runSemanticFanOut(registry2, fn) {
   const eligible = registry2.semanticAvailableEntries();
   const skipped = registry2.list().filter((e) => !e.semanticAvailable).map((e) => ({ vault: e.name, reason: "SEMANTIC_INDEX_NOT_FOUND" }));
-  const results = await Promise.all(
-    eligible.map(async (entry) => ({ vault: entry.name, ...await fn(entry) }))
-  );
-  return { results_by_vault: results, skipped_vaults: skipped };
+  const settled = await Promise.allSettled(eligible.map((entry) => fn(entry)));
+  const fatalError = findFatalRejection(settled);
+  if (fatalError) {
+    throw fatalError;
+  }
+  const results = [];
+  const failed = [];
+  for (let i = 0; i < settled.length; i++) {
+    const outcome = settled[i];
+    const vault = eligible[i].name;
+    if (outcome.status === "fulfilled") {
+      results.push({ vault, ...outcome.value });
+    } else {
+      failed.push(mapRejectionToFailedVault(vault, outcome.reason));
+    }
+  }
+  return { results_by_vault: results, skipped_vaults: skipped, failed_vaults: failed };
 }
 
 // src/modules/semantic/retrieval-policy.ts
@@ -17473,7 +17536,7 @@ async function buildServerInstructions(registry2) {
 
 ## Multi-vault mode
 
-This server is registered with multiple vaults: ${names}. Every tool accepts an optional \`vault\` parameter. For broad recall, \`search_notes\`, \`query_notes\`, and \`get_vault_overview\` fan out across all vaults when \`vault\` is omitted; other tools (reads of specific paths, writes, single-vault diagnostics) require an explicit \`vault\` \u2014 omitting it returns \`VAULT_REQUIRED\`. Path-shaped parameters (\`path\`, \`paths\`, \`path_prefix\`) remain vault-relative; vault identity is always carried by \`vault\`.`;
+This server is registered with multiple vaults: ${names}. Every tool accepts an optional \`vault\` parameter. For broad recall, \`search_notes\`, \`query_notes\`, \`get_vault_overview\`, \`list_tags\`, and \`list_properties\` fan out across all vaults when \`vault\` is omitted; other tools (reads of specific paths, writes, single-vault diagnostics) require an explicit \`vault\` \u2014 omitting it returns \`VAULT_REQUIRED\`. Fan-out responses include \`results_by_vault\`, \`skipped_vaults\` (vaults pre-filtered out, e.g. missing semantic index), and \`failed_vaults\` (per-vault runtime errors with \`{ code, message, details? }\`) \u2014 a single failed vault does not abort the whole call. Path-shaped parameters (\`path\`, \`paths\`, \`path_prefix\`) remain vault-relative; vault identity is always carried by \`vault\`.`;
   }
   for (const entry of registry2.list()) {
     const extra = await readExternalAgentInstructions(entry.path);