Interact with Microsoft 365 and Office services through the Microsoft Graph API.
OmniFocus Operator is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP server exposing OmniFocus as structured task infrastructure for AI agents
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user omnifocus-operator-mcp '--' uvx omnifocus-operator
# 2 — ask your agent for something these tools do
# get_all, get_task, get_project and 8 more
OmniFocus Operator costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts OmniFocus Operator as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user omnifocus-operator-mcp '--' uvx omnifocus-operatorReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Return the full OmniFocus database as structured data. WARNING: This is a last-resort/debugging tool. Prefer list_tasks or list_projects for filtered, paginated results. get_all returns the entire database and should only be used when you need a complete snapshot. … Response contains: tasks,…
Takes no parameters.
Look up a single task by its ID. … Fields: urgency, availability, dueDate, deferDate, plannedDate, inheritedDueDate, flagged, inheritedFlagged, hasNote, hasRepetition, hasAttachments, isSequential, dependsOnChildren, tags [{id, name}], parent (project {id, name} or task {id, name}), project {id,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Look up a single project by its ID. $inbox is not a real project and cannot be looked up here. It has no review schedule, status, or other project properties. To query inbox tasks, use list_tasks with inInbox=true. … Fields: urgency, availability, dueDate, deferDate, plannedDate, flagged, tags…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Look up a single tag by its ID. … Fields: availability, childrenAreMutuallyExclusive, parent {id, name}. childrenAreMutuallyExclusive: when true, child tags behave like radio buttons.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Create tasks in OmniFocus. Best-effort: all items are processed regardless of earlier failures. Each item gets its own status (success or error). … … repetitionRule requires all three root fields (frequency, schedule, basedOn) when creating. on and onDates within frequency are mutually…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | — |
Edit existing tasks in OmniFocus using patch semantics. Fail-fast: processing stops at the first error. Earlier items are committed; later items get status 'skipped' with a warning referencing the failed item. … Patch: omit = no change, null = clear, value = update. … repetitionRule partial…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | — |
List and filter tasks. … … include: optional array of field groups, additive on top of defaults. - "notes": note - "metadata": added, modified, completionDate (+inherited), dropDate (+inherited), url - "hierarchy": parent, hasChildren, type, completesWithChildren - "time":…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | yes | — |
List and filter projects. … … include: optional array of field groups, additive on top of defaults. - "notes": note - "metadata": added, modified, completionDate, dropDate, url - "hierarchy": folder, hasChildren, type, completesWithChildren - "time": estimatedMinutes, repetitionRule -…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | yes | — |
List and filter tags. … Returns a flat list. Each tag includes a parent field {id, name} that can be used to reconstruct hierarchy. Response: {items, total, hasMore} Fields per tag: availability, childrenAreMutuallyExclusive, parent {id, name}. childrenAreMutuallyExclusive: when true, child…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | yes | — |
List and filter folders. … Returns a flat list. Each folder includes a parent field {id, name} that can be used to reconstruct hierarchy. Response: {items, total, hasMore} Fields per folder: availability, parent {id, name}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | yes | — |
List perspectives. … … Response: {items, total, hasMore} Key fields per perspective: id, name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | yes | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under LicenseRef-Proprietary
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OmniFocus Operator or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_all | no tags | |
| get_task | no tags | |
| get_project | no tags | |
| get_tag | no tags | |
| add_tasks | no tags | |
| edit_tasks | no tags | |
| list_tasks | no tags | |
| list_projects | no tags | |
| list_tags | no tags | |
| list_folders | no tags | |
| list_perspectives | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.4.7. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish OmniFocus Operator can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.