Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP OmniFocus create a task named 'Review Q3 report' due tomorrow"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for OmniFocus with auto-detection of Pro/Standard version.
Auto-detection: Automatically detects OmniFocus Pro or Standard
Full Pro support: AppleScript for read/write with sync
Standard fallback: SQLite read + URL scheme for create
Feature | Pro (AppleScript) | Standard |
Read tasks | ✓ | ✓ (SQLite) |
Create task | ✓ | ✓ (URL scheme, syncs) |
Update task | ✓ | ⚠️ (SQLite, no sync) |
Complete task | ✓ | ⚠️ (SQLite, no sync) |
Get projects | ✓ | ✓ (SQLite) |
⚠️ Standard SQLite write: Changes don't sync until OmniFocus restart.
Related MCP server: OmniFocus MCP Server
npx mcp-omnifocusgit clone https://github.com/avlihachev/mcp-omnifocus.git
cd mcp-omnifocus
npm install
npm run buildAdd to ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"omnifocus": {
"command": "npx",
"args": ["mcp-omnifocus"]
}
}
}Or if installed from source:
{
"mcpServers": {
"omnifocus": {
"command": "node",
"args": ["/path/to/mcp-omnifocus/dist/index.js"]
}
}
}Get tasks filtered by flagged, due today, or all.
Create a new task with name, note, project, flagged, dueDate.
Update existing task (Pro: syncs, Standard: SQLite only).
Mark task as complete (Pro: syncs, Standard: SQLite only).
Get list of active projects.
Mark a task as complete. (Standard version: changes via SQLite won't sync until OmniFocus restart)
Inputs: taskId (required).
Create a new task in OmniFocus. Detected version: standard
Inputs: name (required), note, dueDate, flagged, +1 more.
Get current configuration settings
Inputs: no named parameters.
Get list of active projects from OmniFocus. Detected version: standard
Inputs: no named parameters.
Get tasks from OmniFocus. Filter by flagged, due today, or all. Detected version: standard
Inputs: filter.
Update configuration settings. For Standard version: directSqlAccess controls whether to use direct SQLite access for update/complete operations (faster but requires OmniFocus restart to sync)
Inputs: taskLimit, directSqlAccess.
Update an existing task in OmniFocus. (Standard version: changes via SQLite won't sync until OmniFocus restart)
Inputs: taskId (required), name, note, dueDate, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool targets a distinct resource and action: tasks have get/create/update/complete, projects have get, and configuration has get/set. There is no meaningful overlap between the tools, so an agent should be able to select the right one without confusion.
All tools follow the consistent omnifocus_<verb>_<noun> snake_case pattern using clear verbs like get, create, update, complete, and set. The naming conventions are uniform and predictable across the entire set.
Seven tools is a well-scoped size for an OmniFocus server, covering task operations, project retrieval, and configuration without unnecessary bulk. Each tool serves a clear purpose and the count feels appropriate for the domain.
The core task lifecycle is covered well with get, create, update, and complete operations, and config get/set supports the server itself. Minor gaps exist such as no task deletion or project mutation capabilities, but agents can likely work around these for most workflows.
Manage tasks, Focus Zone, notes, projects, and task history from compatible AI assistants.
Read teams, spaces, lists and tasks; create, update and comment on tasks and track time.
Read and edit your Tasks boards: create and update tasks, comment, and track time.
Read and update your Nirvana tasks and projects: GTD states, tags, due dates, and capture.
