Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Edit Note

notes.edit

Edit existing notes by replacing, appending, prepending, or inserting content after a specific heading or block reference in an Obsidian vault.

Instructions

Mutate the body of an existing note. The mode field selects how content is applied: replace overwrites the whole note; append adds to the end; prepend adds after the frontmatter (or at the top if none); after-heading inserts after the first heading whose text matches anchor (no leading #); after-block inserts after the block reference ^anchor. Fails if the note does not exist — use notes.create first. replace mode is idempotent-destructive; the others are additive.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Examples:

Example 1 — Append a new journal entry to the end of today's note:

{
  "mode": "append",
  "path": "Journal/2026-04-24.md",
  "content": "\n## Afternoon\n\nFinished the tool consolidation."
}

Example 2 — Insert content after a specific heading:

{
  "mode": "after-heading",
  "path": "Projects/Alpha.md",
  "anchor": "Open questions",
  "content": "- Do we need to bump the Zod major?\n"
}

Example 3 — Insert after a block reference:

{
  "mode": "after-block",
  "path": "Notes/idea.md",
  "anchor": "idea-1",
  "content": "Follow-up thought …"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesThe path or identifier the tool acted on.
changedYesTrue if the tool altered vault state on this call; false if it was a no-op.
summaryYesShort human-readable summary of what happened.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.3.5
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / description
      Added value: +"Discriminated union on `mode`. `replace` overwrites the whole note body; `append` adds to the end; `prepend` adds to the start (after frontmatter); `after-heading` inserts after a heading (anchor = heading text, no `#`); `after-block` inserts after a block reference (anchor = block id, no `^`)."
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "properties": {
+      "content": {
+        "description": "Replacement body for the entire note.",
+        "type": "string"
+      },
+      "mode": {
+        "const": "replace",
+        "type": "string"
+      },
+      "path": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      },
+      "vaultPath": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "mode",
+      "path",
+      "content"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "content": {
+        "type": "string"
+      },
+      "mode": {
+        "const": "append",
+        "type": "string"
+      },
+      "path": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      },
+      "vaultPath": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "mode",
+      "path",
+      "content"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "content": {
+        "type": "string"
+      },
+      "mode": {
+        "const": "prepend",
+        "type": "string"
+      },
+      "path": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      },
+      "vaultPath": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "mode",
+      "path",
+      "content"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "anchor": {
+        "description": "Heading text (without the leading `#`s) to insert after. Matches the first heading in the note that has this exact text.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "content": {
+        "type": "string"
+      },
+      "mode": {
+        "const": "after-heading",
+        "type": "string"
+      },
+      "path": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      },
+      "vaultPath": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "mode",
+      "path",
+      "content",
+      "anchor"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "anchor": {
+        "description": "Block id (without the `^` prefix) to insert after. Obsidian block refs only.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "content": {
+        "type": "string"
+      },
+      "mode": {
+        "const": "after-block",
+        "type": "string"
+      },
+      "path": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      },
+      "vaultPath": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "mode",
+      "path",
+      "content",
+      "anchor"
+    ],
+    "type": "object"
+  }
+]
    • removedInput schema / properties
      Removed value: -{}
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description adds crucial behavioral detail: 'replace mode is idempotent-destructive; the others are additive,' plus failure conditions and vault precedence rules. This is rich context that annotations don't provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place: purpose, mode semantics, failure condition, vault behavior, and three illustrative examples. It's front-loaded with the core action, and the structured examples make the modes unambiguous. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex (five modes, two anchor types, vault selection), and the description fully covers all required knowledge: mode differences, anchor syntax, default vault behavior, and error scenarios. With an output schema present, return values need no explanation. Nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema description coverage, the description supplements the schema with examples illustrating the exact format for anchor (no leading '#' for headings, no '^' for blocks), clarifies placement for prepend ('after frontmatter'), and demonstrates real-world usage. This goes beyond what the schema's oneOf branches state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('mutate') with a clear resource ('existing note') and enumerates the distinct modes, which immediately differentiates it from notes.create, notes.delete, and other note-related siblings. It's specific enough for an agent to know exactly what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when NOT to use it ('Fails if the note does not exist — use notes.create first') and clarifies vault selection ('Operates on the session-active vault... unless explicit vaultPath'). It doesn't contrast this with blocks.update or blocks.read, which might be plausible alternatives for fine-grained edits, but the guidance given is clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bezata/kObsidian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server