Skip to main content
Fire an Obsidian command by id. Deny-by-default and triple-gated: requires human confirmation (execute:command is a HITL floor), command execution must be enabled for the vault, and the id must be on the vault allowlist. Falls back to Local REST API’s native /commands/{id}/ route when the companion is unreachable. Never silently runnable. Domain: automation.

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 effect is opaque, so the confirmation binds to the argument hash alone.

Input

Output

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