omnifocus-mcp

Map user intent to id-based OmniFocus task mutations with confirmations.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/MarsPain/efficiency_skills --skill omnifocus-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omnifocus-mcp
Source: https://github.com/MarsPain/efficiency_skills/tree/main/omnifocus-mcp
Command: npx skills add https://github.com/MarsPain/efficiency_skills --skill omnifocus-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

OmniFocus users often face ambiguity when creating or updating tasks and projects. This Skill provides a safe, id-based mutation workflow that minimizes accidental changes and ensures reproducible results by requiring explicit IDs for edits and confirmations for high-risk actions.

Core Features & Use Cases

  • Safe read-first workflow that uses MCP tools to locate tasks by status, date, tags, or project.
  • Deterministic mutation protocol that mutates by id only, with preflight previews and post-mutation verification.
  • Fuzzy search-assisted discovery to identify candidate items, while avoiding writes until the user confirms.

Quick Start

Capture a task in Inbox, clarify it to concrete terms, and organize it with id-based updates to demonstrate end-to-end usage.

Frequently Asked Questions about omnifocus-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely update OmniFocus tasks without accidentally modifying the wrong items?

To safely update OmniFocus tasks without accidental modifications, use a deterministic mutation protocol that requires explicit item IDs for any edits. The workflow performs fuzzy search-assisted discovery to locate candidate items first, then strictly mutates by id only after user confirmation.

What is the best way to locate OmniFocus tasks using MCP for a read-first workflow?

Locating OmniFocus tasks via MCP uses a safe read-first workflow that searches by status, date, tags, or project. This fuzzy discovery process identifies candidate items for review without executing any writes until changes are explicitly confirmed.

Can I preview OmniFocus task changes before applying mutations through MCP?

Yes, you can preview OmniFocus task changes before applying mutations. The workflow enforces preflight previews and post-mutation verification, ensuring all high-risk actions are confirmed through a strict, id-based mutation protocol prior to writing.

How do I process an OmniFocus Inbox task from capture to organized project?

To process an OmniFocus Inbox task, capture the task, clarify it to concrete terms, and organize it using id-based updates. This end-to-end workflow uses MCP to locate the item and applies deterministic mutations to safely move it into a project.

Does OmniFocus MCP automation require explicit IDs for all task mutations?

Yes, OmniFocus MCP automation requires explicit IDs for all task mutations. The protocol loads guidance from mutation-assurance references to ensure changes operate strictly by item IDs, minimizing accidental writes during automated workflow execution.