OmniFocus
NPM · @SCARDIS/OMNIFOCUS-MCP · SCANNED SEP 24
Full CRUD MCP server for OmniFocus via Omni Automation — tasks, projects, folders, tags, recurrence.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2377 tokens (~88/item across 27 items; 27 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 34% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "drop_task" implies "drop" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the OmniFocus MCP server?
OmniFocus runs locally as an npm package, launched with npx -y @scardis/omnifocus-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @scardis/omnifocus-mcp
claude mcp add steveardis-omnifocus -- npx -y @scardis/omnifocus-mcp
{
"mcpServers": {
"steveardis-omnifocus": {
"command": "npx",
"args": [
"-y",
"@scardis/omnifocus-mcp"
]
}
}
} {
"servers": {
"steveardis-omnifocus": {
"command": "npx",
"args": [
"-y",
"@scardis/omnifocus-mcp"
]
}
}
} codex mcp add steveardis-omnifocus -- npx -y @scardis/omnifocus-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"steveardis-omnifocus": {
"type": "local",
"command": [
"npx",
"-y",
"@scardis/omnifocus-mcp"
],
"enabled": true
}
}
} openclaw mcp add steveardis-omnifocus --command npx --arg -y --arg @scardis/omnifocus-mcp
mcp_servers:
steveardis-omnifocus:
command: "npx"
args: ["-y", "@scardis/omnifocus-mcp"] {
"McpServers": {
"steveardis-omnifocus": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@scardis/omnifocus-mcp"
]
}
}
} assistant mcp add steveardis-omnifocus -t stdio -c npx -a -y @scardis/omnifocus-mcp
{
"mcpServers": {
"steveardis-omnifocus": {
"command": "npx",
"args": [
"-y",
"@scardis/omnifocus-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.87 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/@scardis/omnifocus-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
complete_project ~34
Mark a project as done (complete). Returns the updated project detail.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The project's id.primaryKey |
No output schema declared.
No examples provided.
complete_task ~36
Mark a task complete by its stable ID. Returns the updated task detail.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task's id.primaryKey |
No output schema declared.
No examples provided.
create_folder ~55
Create a new OmniFocus folder. Omit parentFolderId to create at the top level; provide parentFolderId to nest it inside an existing folder.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| parentFolderId | string | – | – |
No output schema declared.
No examples provided.
create_project ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deferDate | string | – | – |
| dueDate | string | – | – |
| flagged | boolean | – | – |
| folderId | string | – | – |
| name | string | yes | – |
| note | string | – | – |
| reviewInterval | object | – | – |
| status | string | – | – |
| tagIds | array | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
create_tag ~55
Create a new OmniFocus tag. Omit parentTagId to create at the top level; provide parentTagId to nest it under an existing tag.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| parentTagId | string | – | – |
No output schema declared.
No examples provided.
create_task ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deferDate | string | – | – |
| dueDate | string | – | – |
| estimatedMinutes | integer | – | – |
| flagged | boolean | – | – |
| name | string | yes | – |
| note | string | – | – |
| parentTaskId | – | – | – |
| plannedDate | string | – | – |
| projectId | string | – | – |
| repetitionRule | object | – | – |
| tagIds | array | – | – |
No output schema declared.
No examples provided.
delete_folder ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The folder's id.primaryKey |
No output schema declared.
No examples provided.
delete_project ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The project's id.primaryKey |
No output schema declared.
No examples provided.
delete_tag ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The tag's id.primaryKey |
No output schema declared.
No examples provided.
delete_task ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task's id.primaryKey |
No output schema declared.
No examples provided.
drop_project ~32
Mark a project as dropped. Returns the updated project detail.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The project's id.primaryKey |
No output schema declared.
No examples provided.
drop_task ~36
Mark a task dropped by its stable ID. Returns the updated task detail.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task's id.primaryKey |
No output schema declared.
No examples provided.
edit_folder ~32
Rename an existing OmniFocus folder by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
edit_project ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deferDate | – | – | – |
| dueDate | – | – | – |
| flagged | boolean | – | – |
| id | string | yes | – |
| name | string | – | – |
| note | string | – | – |
| reviewInterval | object | – | – |
| status | string | – | – |
| tagIds | array | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
edit_tag ~55
Edit an existing OmniFocus tag. Provide id plus any combination of name (rename) and status (active/onHold/dropped).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| name | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
edit_task ~259
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 repetition, pass clearRepetitionRule: true.
| Name | Type | Req | Description |
|---|---|---|---|
| clearDeferDate | boolean | – | Set to true to clear the task's defer date |
| clearDueDate | boolean | – | Set to true to clear the task's due date |
| clearPlannedDate | boolean | – | Set to true to clear the task's planned date |
| clearRepetitionRule | boolean | – | Set to true to clear the task's repetition rule |
| deferDate | string | – | – |
| dueDate | string | – | – |
| estimatedMinutes | – | – | – |
| flagged | boolean | – | – |
| id | string | yes | – |
| name | string | – | – |
| note | string | – | – |
| plannedDate | string | – | – |
| repetitionRule | object | – | – |
| tagIds | array | – | – |
No output schema declared.
No examples provided.
get_folder ~49
Get full detail for a folder by its stable ID. Returns path, parentId, status, child folder IDs, and immediate project IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The folder's id.primaryKey |
No output schema declared.
No examples provided.
get_project ~50
Get full detail for a project by its stable ID. Returns note, folder path, status, type, dates, review metadata, and tag IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The project's id.primaryKey |
No output schema declared.
No examples provided.
get_tag ~45
Get full detail for a tag by its stable ID. Returns path, parentId, status, and child tag IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The tag's id.primaryKey |
No output schema declared.
No examples provided.
get_task ~77
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task's id.primaryKey |
No output schema declared.
No examples provided.
list_folders ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional filter. When status is provided, only folders with that status are returned. When omitted, all folders (active and dropped) are returned. |
| limit | integer | – | Maximum number of folders to return. Defaults to 200. |
No output schema declared.
No examples provided.
list_projects ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional filters. All fields combine as AND. When status is omitted, done and dropped projects are excluded by default. |
| limit | integer | – | Maximum number of projects to return. Defaults to 100. |
No output schema declared.
No examples provided.
list_tags ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional filter. When status is provided, only tags with that status are returned. When omitted, all tags (active, onHold, and dropped) are returned. |
| limit | integer | – | Maximum number of tags to return. Defaults to 200. |
No output schema declared.
No examples provided.
list_tasks ~192
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). Results are capped at limit (default 200). Each returned task includes dueDate and tagIds.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Optional filters. All fields combine as AND. When status is omitted, complete and dropped tasks are excluded by default. |
| limit | integer | – | Maximum number of tasks to return. Defaults to 200. |
| scope | object | yes | Exactly one of: projectId (string), folderId (string), inbox (true), or all (true) |
No output schema declared.
No examples provided.
move_project ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| folderId | – | yes | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
move_task ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| parentTaskId | – | – | – |
| projectId | – | – | – |
No output schema declared.
No examples provided.
resolve_name ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Exact name to search for |
| scope | string | – | Optional path prefix to narrow results, e.g. "Work ▸ Clients" |
| type | string | yes | The entity type to search: task, project, folder, tag, or perspective |
No output schema declared.
No examples provided.
What is the OmniFocus MCP server?
OmniFocus is an MCP server listed in the public MCP registry as io.github.steveardis/omnifocus. Full CRUD MCP server for OmniFocus via Omni Automation, tasks, projects, folders, tags, recurrence. This page covers its npm package (@scardis/omnifocus-mcp).
Is the OmniFocus MCP server safe to use?
OmniFocus scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OmniFocus MCP server expose?
OmniFocus exposes 27 tools: list_projects, get_project, list_folders, get_folder, list_tasks, and 22 more. Their descriptions and schemas cost roughly 2,377 tokens of context every time the server is loaded.
Is the OmniFocus MCP server still maintained?
OmniFocus is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the OmniFocus MCP server under?
OmniFocus declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.