Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Create Note Or Folder

notes.create

Create markdown notes or folders in an Obsidian vault. Handles existing files with error, replace, or skip options to avoid collisions.

Instructions

Create a new note or folder in the vault. kind:'note' creates a markdown note at path with the given content; ifExists controls collision behavior (error = fail, default; replace = overwrite; skip = no-op). kind:'folder' creates a directory at path (intermediate folders are created automatically; idempotent — re-creating an existing folder is a no-op). Returns the standard mutation envelope.

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 — Create a new note, failing if it exists:

{
  "kind": "note",
  "path": "Journal/2026-04-24.md",
  "content": "# Today\n"
}

Example 2 — Ensure a folder exists (idempotent):

{
  "kind": "folder",
  "path": "Projects/Alpha/Reports"
}

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 `kind`. `note` creates a markdown note (`.md`); `folder` creates a directory. Use `kind:'folder'` when the target should be a directory, not a file."
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "properties": {
+      "content": {
+        "description": "Initial body. Use an empty string for a blank note.",
+        "type": "string"
+      },
+      "ifExists": {
+        "description": "`error` (default) = fail if the note already exists; `replace` = overwrite; `skip` = no-op when the note exists.",
+        "enum": [
+          "error",
+          "replace",
+          "skip"
+        ],
+        "type": "string"
+      },
+      "kind": {
+        "const": "note",
+        "type": "string"
+      },
+      "path": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      },
+      "vaultPath": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "path",
+      "content"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "kind": {
+        "const": "folder",
+        "type": "string"
+      },
+      "path": {
+        "description": "Vault-relative folder path. Intermediate folders are created as needed.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "vaultPath": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "path"
+    ],
+    "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. Changed10 schema fields changedv0.1.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / content
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / overwrite
      Removed value: -{
-  "type": "boolean"
-}
    • removedInput schema / properties / path
      Removed value: -{
-  "maxLength": 255,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / vaultPath
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "path",
-  "content"
-]
    • addedOutput schema / description
      Added value: +"Standard mutation envelope. Individual tools may attach additional fields (e.g. `created`, `appended`, `before`/`after` counts) — those are documented in the tool description."
    • addedOutput schema / properties / changed / description
      Added value: +"True if the tool altered vault state on this call; false if it was a no-op."
    • addedOutput schema / properties / summary / description
      Added value: +"Short human-readable summary of what happened."
    • addedOutput schema / properties / target / description
      Added value: +"The path or identifier the tool acted on."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

The description richly discloses behavior beyond the annotations: `ifExists` semantics (`error`, `replace`, `skip`), idempotent folder creation, automatic creation of intermediate folders, and explicit precedence of `vaultPath` over the session-active vault. It also notes the return is a standard mutation envelope, which is useful given the annotations do not describe side effects.

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 efficiently organized: a lead sentence with the core operation, then mode-specific behavior, then operational context, then examples. Every section adds information, and the examples are compact and illustrative without padding.

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?

For a discriminated-union mutation tool, the description covers all necessary decision points: note vs. folder, collision handling, path behavior, vault selection, and idempotency. The output schema exists, so the vague 'standard mutation envelope' reference is acceptable and does not leave a critical gap.

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?

Although the schema already documents parameters well, the description adds meaningful cross-parameter semantics: how `kind` switches the object shape, how `ifExists` interacts with existing notes, how folder creation behaves idempotently, and how `vaultPath` overrides the active vault. The two concrete JSON examples further clarify expected usage.

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 states a specific action — 'Create a new note or folder in the vault' — and clearly distinguishes the two modes via `kind:'note'` and `kind:'folder'`. It also differentiates from siblings like `notes.edit`, `notes.move`, and `notes.delete` by naming creation as the operation and specifying the resulting artifacts (markdown files or directories).

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?

The description gives clear operational context: it explains that the tool operates on the session-active vault unless `vaultPath` is passed, and the schema-level note says to use `kind:'folder'` when the target should be a directory rather than a file. It does not explicitly contrast this tool with sibling creation-like tools (e.g., `tasks.create`, `templates.use`), so it stops short of full alternative routing.

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