Skip to main content
Glama
bezata

kObsidian MCP

Select Active Vault

vault.select

Set the session-active vault for Obsidian filesystem tools by identifying the target with its id, case-insensitive name, or absolute directory path.

Instructions

Set the session-active vault for subsequent filesystem tool calls. Identify the target by EXACTLY ONE of id (stable id from vault.list), name (case-insensitive match), or path (absolute directory path — need not appear in vault.list; lets the LLM point at a fresh/empty vault to initialise). Precedence chain becomes: per-call vaultPath argument (highest) → this session selection → OBSIDIAN_VAULT_PATH → error. Explicit vaultPath arguments on individual tool calls always override this selection. Respects KOBSIDIAN_VAULT_ALLOW / KOBSIDIAN_VAULT_DENY operator gating (though OBSIDIAN_VAULT_PATH is never filtered). Does NOT change which vault the live Obsidian process has open — workspace.* and commands.* tools remain tied to OBSIDIAN_API_URL. HTTP deployments: this server shares the selection across HTTP clients, so concurrent multi-client HTTP setups should pass vaultPath per call instead.

Examples:

Example 1 — Switch to the vault named 'Work':

{
  "name": "Work"
}

Example 2 — Select by id from vault.list:

{
  "id": "58f115bd2c2febd2"
}

Example 3 — Point at an ad-hoc path (e.g. a fresh vault to initialise):

{
  "path": "/Users/alice/FreshVault"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoVault id returned by `vault.list`. Mutually exclusive with `name` and `path`.
nameNoCase-insensitive vault name match against `vault.list`. Mutually exclusive with `id` and `path`.
pathNoAbsolute vault directory path. Need not appear in `vault.list` — accepting an ad-hoc path lets the LLM point at a fresh vault. Must exist and be a directory. Mutually exclusive with `id` and `name`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
changedYes
targetYes
summaryYes
activeYesA single vault entry returned by `vault.list` and `vault.current.active`.
previousYesThe previously-selected vault, or null if none was selected.
Behavior5/5

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

Adds context beyond annotations: does not change live Obsidian vault, respects environment variable gating, shares selection across HTTP clients. Annotations are consistent and description enriches understanding.

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

Conciseness4/5

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

Well-structured with clear sections and examples. Slightly verbose but every sentence adds value. Front-loads purpose effectively.

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?

Given output schema exists, description covers all necessary aspects: purpose, usage, behavioral details, parameter semantics, and examples. No gaps.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds extra meaning: stable id, case-insensitive name, ad-hoc path. Examples further clarify 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?

Clearly states it sets the session-active vault for filesystem tool calls. Distinguishes from siblings by specifying the three identification methods (id, name, path) and how they relate to vault.list and vault.reset.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use each identifier, precedence chain, and notes for HTTP deployments. Also clarifies that workspace.* and commands.* tools are unaffected.

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