Full CRUD MCP server for OmniFocus via Omni Automation — tasks, projects, folders, tags, recurrence.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"omnifocus": {
"args": [
"-y",
"@scardis/omnifocus-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server for OmniFocus that exposes the full Omni Automation JavaScript API to LLM callers.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP Security Weekly
Get CVE alerts and security updates for io.github.steveardis/omnifocus and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server for OmniFocus that exposes the full Omni Automation JavaScript API to LLM callers.
macOS only. Requires OmniFocus running on the same machine. The entire implementation runs OmniJS snippets inside OmniFocus via osascript -l JavaScript — no AppleScript string generation, no scripting dictionary limitations.
The package is published to npm as @scardis/omnifocus-mcp.
Add to your MCP client config (e.g. Claude Desktop claude_desktop_config.json):
{
"mcpServers": {
"omnifocus": {
"command": "npx",
"args": ["-y", "@scardis/omnifocus-mcp"]
}
}
}
git clone https://github.com/steveardis/omnifocus-mcp.git
cd omnifocus-mcp
npm install
npm run build
Then configure your MCP client:
{
"mcpServers": {
"omnifocus": {
"command": "node",
"args": ["/absolute/path/to/omnifocus-mcp/dist/server.js"]
}
}
}
| Tool | Description |
|---|---|
list_projects | Projects with optional filtering by status, folderId, flagged. Default excludes done/dropped. Limit (default 100). |
get_project | Full project detail by stable ID |
list_tasks | Tasks scoped by projectId, folderId, inbox: true, or all: true with optional status/tag/due/flagged filters. Limit (default 200). |
get_task | Full task detail by stable ID — includes defer/planned/due dates, tags, repetition rule, parentTaskId |
list_folders | Folders with optional status filter. Limit (default 200). |
get_folder | Full folder detail by stable ID, including child folder and project IDs |
list_tags | Tags with optional status filter. Limit (default 200). |
get_tag | Full tag detail by stable ID, including child tag IDs |
resolve_name | Resolve a name to stable ID candidates — never silently disambiguates; returns all matches |
| Tool | Description |
|---|---|
create_task | Create a task in inbox, project, or as subtask. Supports defer/planned/due dates, tags, flagged, estimated minutes, and repetition rules. |
edit_task | Edit any task field. Pass null to clear dates or repetition. Omitted fields are unchanged. |
complete_task | Mark a task complete |
drop_task | Mark a task dropped |
delete_task | Permanently delete a task and all subtasks |
create_project | Create a project, optionally in a folder. Supports type, status, review interval, tags. |
edit_project | Edit project fields |
complete_project | Mark a project complete |
drop_project | Mark a project dropped |
delete_project | Permanently delete a project and all its tasks |
create_folder | Create a folder, optionally nested |
edit_folder | Rename a folder |
delete_folder | Permanently delete a folder and entire subtree |
create_tag | Create a tag, optionally nested |
edit_tag | Edit tag name or status |
delete_tag | Permanently delete a tag and child tags |
move_task | Move a task to a project or make it a subtask of another task |
move_project | Move a project to a folder or to top level |
Every entity returned by this server includes a stable id field (id.primaryKey from OmniFocus). Use this ID in subsequent calls rather than names. Names can be ambiguous; IDs are not.
If you have a name but not an ID, use resolve_name. It returns a list — if multiple candidates are returned, inspect the path field and ask the user to disambiguate before proceeding with any write operation.
Two notable alternatives exist: themotionmachine/OmniFocus-MCP and [jqlts1/omni