omnifocus-sync-mcp
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., "@omnifocus-sync-mcp list my flagged tasks"
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.
omnifocus-sync-mcp
A headless MCP server that reads and writes OmniFocus data by talking directly to the Omni Sync Server over WebDAV — no Mac, no running OmniFocus app. It implements OmniFocus's client-side end-to-end encryption in TypeScript, so it can run anywhere Node runs (a Linux NAS, a container, a cloud box).
Every other OmniFocus MCP server automates the local macOS app via AppleScript/JXA. This one speaks the cloud sync protocol instead, which is what lets it run headless.
⚠️ Alpha / use at your own risk. This talks to your real task database. The read and write paths have been validated end-to-end against a live Omni Sync Server account (add + delete transactions round-trip correctly), and the crypto and parsing have an offline test suite — but this hasn't been exercised across every OmniFocus version or edge case. Keep a backup (in OmniFocus: File → Back Up Database), and consider a throwaway account while evaluating. See Safety.
How it works
An OmniFocus sync store is a WebDAV collection (OmniFocus.ofocus/) containing:
a baseline transaction and a chain of delta transactions, each a
.zipholding acontents.xmldescribing object creates/updates/deletes;.clientfiles registering each device and the transaction "tail" it has synced to;an
encryptedplist holding the wrapped document keys.
This server:
Resolves the shard —
sync.omnigroup.com302-redirects each account to asyncN.omnigroup.comhost; the client follows it.Authenticates with HTTP Digest (what Omni Sync Server negotiates).
Decrypts using the OmniFileStore format: PBKDF2 derives a wrapping key from your passphrase, RFC 3394 unwraps the document key slots, and each file is AES-128-CTR + HMAC-SHA256 in 64 KiB segments (encrypt-then-MAC).
Replays the transaction chain into an in-memory object model.
Writes by building a new
contents.xml, zipping, encrypting,PUT-ting it as a new transaction descending from the current head tail, and refreshing its.clientregistration so other clients treat it as a real participant.
The crypto and format were reimplemented from Omni's own open-source frameworks
(OmniGroup/OmniGroup, notably
OmniFileStore/EncryptionFormat.md and DecryptionExample.py) plus community
reverse-engineering (tomzx/ofocus-format,
rubyfocus). See CREDITS.
Related MCP server: OmniFocus MCP Server
Install
git clone https://github.com/rosskukulinski/omnifocus-sync-mcp.git
cd omnifocus-sync-mcp
npm install
npm run buildConfigure
Set credentials via environment variables (see .env.example):
Variable | Required | Description |
| yes | Omni Sync Server account name |
| yes | Omni Sync Server account password |
| no | Defaults to the sync password (OmniFocus's default) |
| no | Defaults to |
| no | Defaults to |
| no | Display name for this client's |
| no | Where the stable client id is stored |
| no |
|
Try it without an MCP client
A diagnostic CLI exercises the sync path directly:
export OMNIFOCUS_SYNC_USERNAME=... OMNIFOCUS_SYNC_PASSWORD=...
npm run probe -- sync # show database counts
npm run probe -- list flagged # list flagged tasks
npm run probe -- projects # list projects
npm run probe -- add "Buy milk" # add an inbox taskUse as an MCP server
Run over stdio. Example Claude Desktop / Claude Code config:
{
"mcpServers": {
"omnifocus": {
"command": "node",
"args": ["/absolute/path/to/omnifocus-sync-mcp/dist/index.js"],
"env": {
"OMNIFOCUS_SYNC_USERNAME": "your-account",
"OMNIFOCUS_SYNC_PASSWORD": "your-password"
}
}
}
}Tools
Tool | Description |
| Reload the database from the server; returns counts |
| List tasks ( |
| Full detail for one task by id |
| List projects with folder path and status |
| Create a task (inbox or in a project) |
| Mark a task complete |
| Edit name/note/flag/due/defer; clear dates |
| Delete a task by id |
Safety
Back up first, and prefer a test account until you trust the write path.
Start with
OMNIFOCUS_READ_ONLY=1to explore safely.Writes are append-only transactions; a bad write forks history rather than destroying data, and OmniFocus merges forks on its next sync — but that is a safety net, not a guarantee.
Secrets come from the environment only; nothing is written to this repo. The client identity file (
client.json) contains no secrets.
Development
npm test # offline test suite (crypto round-trips, parse/write, digest)
npm run dev -- ... # run the CLI via tsx without buildingThe offline tests cover the risky parts without a network or a real account: the
OmniFileStore encrypt/decrypt round-trip at every segment boundary, MAC tamper
detection, the passphrase→PBKDF2→key-unwrap pipeline, contents.xml build/parse
round-trips, partial-update merge semantics, and the full zip→encrypt→decrypt→parse
read path.
Credits
Built by reimplementing formats documented and open-sourced by others:
OmniGroup/OmniGroup — Omni's own frameworks;
OmniFileStore/EncryptionFormat.mdandDecryptionExample.pyare the authoritative encryption spec, andOmniFoundation/XML/OFXMLIdentifier.mthe id format.tomzx/ofocus-format — the
.ofocustransaction/format write-up.jyruzicka/rubyfocus, kumpelblase2/focus — prior-art parsers.
Not affiliated with or endorsed by The Omni Group. "OmniFocus" is their trademark.
License
MIT — see LICENSE.
Available Tools
8 toolsof_add_taskAdd an OmniFocus taskA
Create a task. Without a project it goes to the inbox. Dates accept ISO 8601 strings.
Inputs: name (required), due, tag, note, +4 more.
of_complete_taskComplete an OmniFocus taskB
Mark a task complete (optionally at a specific ISO 8601 time).
Inputs: id (required), when.
of_delete_taskDelete an OmniFocus taskA
Permanently delete a task by id (writes an op=delete transaction).
Inputs: id (required).
of_edit_taskEdit an OmniFocus taskA
Edit fields of a task. Use clearDue/clearDefer to remove a date. Only provided fields change.
Inputs: id (required), due, name, note, +5 more.
of_get_taskGet an OmniFocus taskA
Get a single task by its id, with full detail.
Inputs: id (required).
of_list_projectsList OmniFocus projectsA
List all projects with their folder path and status.
Inputs: includeDropped.
of_list_tasksList OmniFocus tasksA
List tasks with optional filtering. filter: remaining (default), available, flagged, inbox, due_soon, all.
Inputs: tag, limit, filter, search, +3 more.
of_syncSync OmniFocusA
Reload the OmniFocus database from the Omni Sync Server. Returns counts of tasks, projects, and tags.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct operation: sync, list/get tasks, list projects, and task CRUD (add, complete, edit, delete). No two tools overlap in purpose, making selection unambiguous.
Most tools follow the verb_noun pattern (list_tasks, get_task, add_task, etc.) with a consistent 'of_' prefix. 'of_sync' is a minor deviation, being a single verb without an explicit object, but the pattern is otherwise uniform.
8 tools is well within the ideal range for a focused sync server, covering core task and project operations without over-fragmentation. Each tool earns its place.
The tool surface covers the main task lifecycle (create, read, update, complete, delete) and project listing, which is adequate for most workflows. Minor gaps include no project creation/editing or dedicated tag listing, but these are not critical dead ends.
Maintenance
Related MCP Connectors
Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Remote MCP server for saving, searching, syncing, and managing Teak cards.
Remote MCP server to read and edit GanttFather projects: tasks, dates, dependencies, critical path.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables automation and management of OmniFocus tasks, projects, and tags using natural language and programmable interfaces from VS Code, command line, or any MCP-compatible client.12MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides full read/write access to OmniFocus, enabling AI assistants to manage tasks, projects, folders, tags, and perspectives via 51 tools, resources, and prompts.5125 npm22MIT
- FlicenseNot gradedqualityBmaintenanceA production-grade MCP server that exposes OmniFocus as structured task infrastructure for AI agents, enabling read, write, and filter operations on tasks and projects via natural language.11-
- AlicenseNot gradedqualityDmaintenanceMCP server that gives AI assistants full control over OmniFocus on macOS, including tasks, projects, tags, folders, perspectives, forecast, notifications, and review workflows.44MIT