Skip to main content
Open a vault note in the running Obsidian app. Tries the companion plugin first (a live Obsidian session for the vault); falls back to the OS obsidian:// URI handler only when uri.allowOsLaunch is enabled and the call arrives over stdio. When neither is available it returns available:false with a reason and a hint instead of a silent success. Always requires human confirmation (execute:uri is a HITL floor): it causes a host-side effect. The path must pass the read ACL and name an existing note. generate_uri remains the pure URI builder.

Annotations

Idempotent is the advisory MCP idempotentHint. Destructive is also yes for a tool that asks for confirmation only on some calls.

Confirmation (human in the loop)

A single-use elicit_token (or a transport-verified confirmation) is required on every call.
  • The confirmation binds to the vault paths the call names, which are also checked against the folder ACL.

Input

Output

Other tools in the automation domain: bundle_files, bundle_folder, eval_dataview_field, execute_command, execute_template, generate_uri, list_commands, list_quickadd_actions, list_tasks, list_templates, makemd_list_spaces, makemd_query, remotely_save_status, remotely_save_trigger, tasks_filter, trigger_quickadd, update_task, validate_dql. Back to the tool catalog.