neuro-vault-mcp 10.0.2 → 10.1.0

package/dist/cli.js

@@ -14530,7 +14530,7 @@ function normalizeScanPrefix(raw) {
 }
 
 // src/lib/obsidian/frontmatter.ts
-import { parse as parseYaml } from "yaml";
+import { parse as parseYaml, stringify as stringifyYaml } from "yaml";
 
 // src/lib/obsidian/in-place-edit.ts
 var FRONTMATTER_OPEN = /^---[ \t]*\r?\n/;
@@ -14611,6 +14611,11 @@ function splitFrontmatter(raw) {
   }
   return { frontmatter: parsed, content };
 }
+function serializeFrontmatter(fm) {
+  return `---
+${stringifyYaml(fm)}---
+`;
+}
 
 // src/lib/obsidian/wikilink.ts
 var WIKILINK_RE = /\[\[(.+?)\]\]/g;
@@ -16517,12 +16522,13 @@ function buildCreateNoteTool(deps) {
     name: external_exports.string().optional(),
     path: external_exports.string().optional(),
     content: external_exports.string().optional(),
+    frontmatter: external_exports.record(external_exports.string(), external_exports.unknown()).optional(),
     overwrite: external_exports.boolean().optional()
   });
   return {
     name: "create_note",
     title: "Create Note",
-    description: "Create a new note. Provide `name` or `path` (exactly one). Optionally provide `content` (raw markdown for the note body and frontmatter). Paths without an extension are treated as `.md` notes.\n\nBefore composing `content`, sample 1\u20132 similar notes from the vault to mimic existing conventions instead of inventing your own. A reliable pattern: `search_notes` for the topic (or `query_notes` with a tag/folder filter that fits) to find candidates, then `read_notes` on the closest match to inspect its frontmatter shape, tag values, heading layout, and folder placement. Match those conventions \u2014 the user almost always prefers a new note that looks like its neighbours. Be especially careful with the `type` frontmatter field: vaults tend to use a small closed set (e.g. project / task / idea / reflection / daily / review / inbox / resource); pick from what other notes use rather than coining a new value.\n\nTemplates are not handled by this tool \u2014 render any template yourself (Obsidian Core Templates, Templater, or anything else) and pass the result as `content`." + describeMultiVault(
+    description: "Create a new note. Provide `name` or `path` (exactly one). Optionally provide `content` (raw markdown for the note body) and/or `frontmatter` (an object of frontmatter properties, serialized to a YAML block and prepended to the note \u2014 prefer this over hand-writing a `---` block inside `content`; it quotes `[[wikilinks]]`, formats dates, and renders tag lists correctly). If `content` also begins with its own `---` block, the two are merged key-by-key and the `frontmatter` parameter wins on any key collision (the body is kept). Paths without an extension are treated as `.md` notes.\n\nBefore composing `content`, sample 1\u20132 similar notes from the vault to mimic existing conventions instead of inventing your own. A reliable pattern: `search_notes` for the topic (or `query_notes` with a tag/folder filter that fits) to find candidates, then `read_notes` on the closest match to inspect its frontmatter shape, tag values, heading layout, and folder placement. Match those conventions \u2014 the user almost always prefers a new note that looks like its neighbours. Be especially careful with the `type` frontmatter field: vaults tend to use a small closed set (e.g. project / task / idea / reflection / daily / review / inbox / resource); pick from what other notes use rather than coining a new value.\n\nTemplates are not handled by this tool \u2014 render any template yourself (Obsidian Core Templates, Templater, or anything else) and pass the result as `content`." + describeMultiVault(
       registry2,
       'Pass `vault: "<name>"` to target a specific vault when multiple are registered.'
     ) + " If a note with this path/name might already exist and the user has not explicitly asked to replace it, ask the user before passing `overwrite: true` \u2014 overwrite is destructive. Default behavior fails when the note exists.",
@@ -16548,7 +16554,14 @@ function buildCreateNoteTool(deps) {
         }
       }
       if (input.overwrite !== void 0) passthrough.overwrite = input.overwrite;
-      if (input.content !== void 0) passthrough.content = input.content;
+      const hasFrontmatter = input.frontmatter !== void 0 && Object.keys(input.frontmatter).length > 0;
+      if (hasFrontmatter) {
+        const { frontmatter: contentFm, content: body } = splitFrontmatter(input.content ?? "");
+        const merged = { ...contentFm ?? {}, ...input.frontmatter };
+        passthrough.content = serializeFrontmatter(merged) + body;
+      } else if (input.content !== void 0) {
+        passthrough.content = input.content;
+      }
       const result = await entry.provider.createNote(passthrough);
       return { vault: entry.name, ...result };
     }