omnifocus-sync-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMNIFOCUS_DATABASE | No | Defaults to OmniFocus.ofocus | |
| OMNIFOCUS_SYNC_URL | No | Defaults to https://sync.omnigroup.com | |
| OMNIFOCUS_READ_ONLY | No | 1/true to refuse all writes | |
| OMNIFOCUS_CLIENT_NAME | No | Display name for this client's .client file | |
| OMNIFOCUS_SYNC_PASSWORD | Yes | Omni Sync Server account password | |
| OMNIFOCUS_SYNC_USERNAME | Yes | Omni Sync Server account name | |
| OMNIFOCUS_CLIENT_STATE_FILE | No | Where the stable client id is stored | |
| OMNIFOCUS_ENCRYPTION_PASSPHRASE | No | Defaults to the sync password (OmniFocus's default) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| of_syncA | Reload the OmniFocus database from the Omni Sync Server. Returns counts of tasks, projects, and tags. |
| of_list_tasksA | List tasks with optional filtering. filter: remaining (default), available, flagged, inbox, due_soon, all. |
| of_get_taskA | Get a single task by its id, with full detail. |
| of_list_projectsA | List all projects with their folder path and status. |
| of_add_taskA | Create a task. Without a project it goes to the inbox. Dates accept ISO 8601 strings. |
| of_complete_taskB | Mark a task complete (optionally at a specific ISO 8601 time). |
| of_edit_taskA | Edit fields of a task. Use clearDue/clearDefer to remove a date. Only provided fields change. |
| of_delete_taskA | Permanently delete a task by id (writes an op=delete transaction). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.