Read a note's content, frontmatter, tags, and metadata from the vault. Returns parsed frontmatter, markdown content, tags (from frontmatter and inline), and file stats.

Create a new note in the vault with optional YAML frontmatter. Parent folders are created automatically. Fails if the note already exists (unless overwrite=true).

Update an existing note. Supports three modes: 'replace' (overwrite body), 'append' (add to end), or 'prepend' (add to beginning). Can also merge new frontmatter fields into existing frontmatter.

Delete a note from the vault. By default moves to .trash/ (Obsidian convention) instead of permanent deletion. Set permanent=true for hard delete.

Full-text search across all notes in the vault. Supports plain text and regex patterns. Returns matching files with line numbers and context. Can filter by folder.

List files and folders in the vault. Supports recursive listing with depth control. Hidden folders (.obsidian, .trash, .git) are excluded by default.

Read, add, or remove tags on a note. Tags are managed in YAML frontmatter. Also reads inline #tags from the note content. Handles deduplication automatically.

Get, create, or append to a daily note. Supports 'today', 'yesterday', 'tomorrow', or any date string (YYYY-MM-DD). Daily notes are stored in a configurable folder.

Git version control for your vault. Actions: 'status' (show changes), 'commit' (stage all + commit), 'pull' (fetch remote changes), 'push' (push to remote), 'sync' (pull+commit+push in one operation), 'log' (commit history), 'diff' (show changes), 'init' (initialize git repo + .gitignore), 'remote_add' (add remote), 'remote_list' (list remotes).

Navigate Obsidian [[wikilinks]]. Actions: 'resolve' (find file a wikilink points to), 'backlinks' (find all notes linking to a note), 'outlinks' (list all links from a note), 'unresolved' (find broken wikilinks across the vault). Supports [[note]], [[note|alias]], [[note#heading]], and [[note#^blockid]] syntax.

Create a new task in the vault's task queue with structured YAML frontmatter. Tasks are markdown notes in the Tasks/ folder. Supports priority, type, dependencies, scope isolation, context notes, and acceptance criteria. Auto-refreshes the task dashboard.

Query tasks by status, priority, type, or assignee. Returns a filtered, sorted list of tasks from the vault's task queue. Use to find available work or monitor progress.

Atomically claim a pending task for an agent. Sets status to 'claimed' and records the assignee. Prevents race conditions — if two agents try to claim the same task, the second gets a clear error. Checks dependency completion before allowing claim.

Update a task's status, priority, type, or assignee. Append progress entries to the Agent Log. Validates status transitions (e.g. cannot go from 'pending' to 'completed' — must claim first). Use this to move tasks through the workflow.

Mark a task as completed (or failed/cancelled) with a summary and optional deliverables. Records completed_at timestamp, appends to Agent Log, links deliverable files/URLs, and automatically unblocks dependent tasks.

Create a project with multiple sub-tasks in one call. Use depends_on_indices to wire up task dependencies by array position. Independent tasks can be claimed by different agents in parallel. Returns all task IDs for immediate claiming. Append mode: pass project_id to add new sub-tasks to an existing project.

Get rollup status of a project: progress percentage, status breakdown, active agents, overdue tasks, and blockers. Use list_tasks(type: 'project') to find project IDs.

Get a structured briefing of the vault's current state. Returns active projects, in-progress work, pending tasks, blockers, failures, recent decisions, recent discoveries, and pinned notes. Call this FIRST in any new session to understand what's going on.

Log an architectural or design decision as a structured record. Captures context, rationale, alternatives considered, and consequences. Future agents can find these via get_context to understand WHY things were done.

Log a discovery, gotcha, or TIL (Today I Learned) as a structured note. Captures what was found, its impact, and recommendations. Prevents future agents from re-discovering the same things.

Approve or reject a task in needs_review status. Used by humans to gate high-risk work. Approve sends to completed and unblocks dependents. Reject sends to revision_requested.

Register an agent with capabilities, tags, and capacity. Creates or updates an agent profile in the Agents/ folder. Used for capability-based task routing.

List registered agents. Filter by capability, tag, status, or availability. Shows current workload and capacity for each agent.

Given a task ID, suggest the best agents to assign based on capability match, tag overlap, availability, and success rate. Returns ranked suggestions.

Scan for overdue and failed tasks. Auto-retry failed tasks within max_retries, escalate exhausted tasks to escalate_to agent/human, release timed-out tasks. Use dry_run=true to preview actions without making changes.

Record token/cost usage for a task or agent. Stores structured usage records in the Usage/ folder. Optionally appends usage summary to the task's Agent Log.

Aggregate token and cost usage across tasks, agents, projects, and time ranges. Returns totals and breakdowns by agent and model.