OmniFocus MCP server

Read from the package source without running it. The installed server may list more.

• complete_project

  Mark a project as done (complete). Returns the updated project detail.

• complete_task

  Mark a task complete by its stable ID. Returns the updated task detail.

• create_folderwrite action

  Create a new OmniFocus folder. Omit parentFolderId to create at the top level; provide parentFolderId to nest it inside an existing folder.

• create_projectwrite action

  Create a new OmniFocus project. Omit folderId to create at the top level; provide folderId to place it inside a folder. Optionally set type (parallel/sequential/singleActions), status (active/onHold), review interval, and tags.

• create_tagwrite action

  Create a new OmniFocus tag. Omit parentTagId to create at the top level; provide parentTagId to nest it under an existing tag.

• create_taskwrite action

  Create a new task. Placement: omit projectId and parentTaskId for inbox; provide projectId to add to a project; provide parentTaskId to create a subtask. Providing both projectId and parentTaskId is an error.

• delete_folderwrite action

  Permanently and recursively delete an OmniFocus folder. THIS ACTION CANNOT BE UNDONE. The ENTIRE subtree is destroyed: all child folders, all projects within those folders, and all tasks within those projects. Before calling this tool you MUST ask the user to explicitly confirm they want to permanently delete the folder and all of its contents.

• delete_projectwrite action

  Permanently delete a project and ALL its tasks. THIS ACTION CANNOT BE UNDONE. Before calling this tool you MUST ask the user to explicitly confirm they want to permanently delete the project, and inform them that all tasks within the project will also be deleted.

• delete_tagwrite action

  Permanently delete an OmniFocus tag. THIS ACTION CANNOT BE UNDONE. All child tags are also deleted, and all tasks/projects that held this tag have it removed automatically. Before calling this tool you MUST ask the user to explicitly confirm they want to permanently delete the tag and all its child tags.

• delete_taskwrite action

  Permanently delete a task and all its subtasks. THIS ACTION CANNOT BE UNDONE. Before calling this tool you MUST ask the user to explicitly confirm they want to permanently delete the task, and inform them that all subtasks will also be deleted.

• drop_projectwrite action

  Mark a project as dropped. Returns the updated project detail.

• drop_taskwrite action

  Mark a task dropped by its stable ID. Returns the updated task detail.

• edit_folder

  Rename an existing OmniFocus folder by its ID.

• edit_project

  Edit an existing project. Only provided fields are changed. Pass null for deferDate, dueDate, or reviewInterval to clear them. When tagIds is provided it replaces the full tag set.

• edit_tag

  Edit an existing OmniFocus tag. Provide id plus any combination of name (rename) and status (active/onHold/dropped).

• edit_task

  Edit an existing task by its stable ID. Only fields included in the call are changed; omitted fields are left unchanged. When tagIds is provided it replaces the full tag set. To clear a date field, pass clearDeferDate, clearPlannedDate, or clearDueDate set to true. Pass null for estimatedMinutes to clear it. To set a repetition rule, pass repetitionRule with frequency/interval/method. To clear rep

• get_folder

  Get full detail for a folder by its stable ID. Returns path, parentId, status, child folder IDs, and immediate project IDs.

• get_project

  Get full detail for a project by its stable ID. Returns note, folder path, status, type, dates, review metadata, and tag IDs.

• get_tag

  Get full detail for a tag by its stable ID. Returns path, parentId, status, and child tag IDs.

• get_task

  Get full detail for a task by its stable ID. Returns note, status, flagged, defer/due/completion dates, estimated minutes, container info, tag IDs, and parentTaskId (null for top-level tasks, set to the parent task's ID for subtasks).

• list_folders

  List folders in OmniFocus. By default, all folders (active and dropped) are returned. Optional filter.status ('active' | 'dropped') restricts to that status. Results are capped at limit (default 200). Each folder includes id, name, full path (ancestors joined with ▸), parentId, and status.

• list_projects

  List projects in OmniFocus. By default, done and dropped projects are excluded — pass filter.status to override. Optional filter fields: status (array of status strings), folderId (restricts to that folder's subtree), flagged (boolean). Results are capped at limit (default 100). Each project includes folderId and flagged in addition to id, name, folderPath, status, and type.

• list_tags

  List tags in OmniFocus. By default, all tags (active, onHold, and dropped) are returned. Optional filter.status ('active' | 'onHold' | 'dropped') restricts to that status. Results are capped at limit (default 200). Each tag includes id, name, full path (ancestors joined with ▸), parentId, and status.

• list_tasks

  List tasks in OmniFocus within a scope. Provide exactly one of: projectId (tasks in a project), folderId (tasks across all projects in a folder), inbox (inbox tasks), or all (every task). By default, complete and dropped tasks are excluded — pass filter.status to override. Optional filter fields: flagged (boolean), status (array of status strings), tagId (string), dueBeforeDate (ISO datetime). Res

• move_project

  Move a project to a different folder or to the top level. Pass folderId as a string to move into a folder, or null to move to the top level. Throws a not-found error if either ID does not exist.

• move_task

  Move a task to a different project (making it a top-level task) or make it a subtask of another task. Exactly one of projectId or parentTaskId must be provided. Throws a not-found error if any ID does not exist.

• resolve_name

  Resolve an entity name to its stable ID(s). Returns ALL matches — never silently picks one. If multiple candidates are returned, ask the user or caller to disambiguate using the path field before proceeding with a write operation.

• Code scan102 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 62 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

88/100

higher than 75% of 48,243 servers

Tools

27

the typical server has 7

Tools that change things

37%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

2

more than 75% of 28,706 servers

Downloads a week

44

more than 34% of 12,306 servers with a package

OmniFocus: common questions

Is OmniFocus MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the OmniFocus safety report

How do I install OmniFocus?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does OmniFocus need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is OmniFocus maintained?

The last commit was 68 days ago (2026-08-29). The latest release is v0.2.1.

How does OmniFocus compare with other MCP servers?

safety score 88/100 (higher than 75% of 48,243 servers); tools 27 (the typical server has 7); tools that change things 37% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.