MCP Server for ZenTao bug management with CAS SSO login
from $14/mo
Nothing to run from here
Omnifocus Mcp Enhanced 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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
🚀 NEW: Native Custom Perspective Access! Enhanced MCP server with OmniFocus custom perspective support, hierarchical task display, AI-optimized tool selection, and comprehensive task management
Quickstart
# 1 — run it from where its publisher ships it
npx -y omnifocus-mcp-enhanced
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> 🚀 NEW: Native Custom Perspective Access! Enhanced MCP server with OmniFocus custom perspective support, hierarchical task display
Publishernot claimed
JQAll 1 server
jqlts11 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 Mcp Enhanced 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. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add omnifocus-mcp-enhanced -- npx -y omnifocus-mcp-enhancedReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
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.
What you approve
25 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.
Gets the current state of your OmniFocus database
Takes no parameters.
Example callreturns →
Add a new task to OmniFocus
Takes no parameters.
Example callreturns →
Add a new project to OmniFocus
Takes no parameters.
Example callreturns →
Remove a task or project from OmniFocus
Takes no parameters.
Example callreturns →
Edit a task or project in OmniFocus
Takes no parameters.
Example callreturns →
Move an existing task to a project, parent task, or inbox
Takes no parameters.
Example callreturns →
Move a confirmed set of tasks to projects, parent tasks, or Inbox. The complete batch is validated before any change and every destination is verified afterward.
Takes no parameters.
Example callreturns →
Mark tasks complete or incomplete by stable ID. Accepts up to 100 items with optional completion dates. Preflights every ID, verifies every result, and restores previous states on failure. Repeating tasks generate new instances when completed.
Takes no parameters.
Example callreturns →
Edit fields and tags on up to 100 tasks or projects by stable ID. Each item names one object with taskId or projectId and carries only the fields it changes; an omitted field is untouched and an explicit null clears it. Dates accept an absolute value or a signed shift such as \
Takes no parameters.
Example callreturns →
Add multiple tasks or projects to OmniFocus in a single operation
Takes no parameters.
Example callreturns →
Remove a user-confirmed set of tasks or projects by stable ID. The complete batch is validated before deletion and every ID is verified absent afterward.
Takes no parameters.
Example callreturns →
Create one user-confirmed project tree with stable folder/tag IDs. The complete outline is preflighted, created in one OmniFocus request, and read back for verification.
Takes no parameters.
Example callreturns →
Get information about a specific task by ID or name
Takes no parameters.
Example callreturns →
Read a task attachment reported by get_task_by_id. Images are returned as MCP image content when possible.
Takes no parameters.
Example callreturns →
Read tasks from inbox, flagged, forecast, tag, or custom perspective. Use source to select the view; source-specific parameters are strictly validated.
Takes no parameters.
Example callreturns →
Set, update, or clear the repeat rule on a task. Supports ICS rule strings, schedule type, anchor date, catch-up, end date, and repetition count.
Takes no parameters.
Example callreturns →
List, search, add, edit, or remove OmniFocus tags. This mixed-operation tool is conservatively marked destructive: list/search are read-only, add/edit mutate, and remove deletes the selected tag plus child tags but keeps tasks.
Takes no parameters.
Example callreturns →
Advanced task filtering by status, dates, projects, tags, search, and more, with optional subtask-tree expansion
Takes no parameters.
Example callreturns →
List OmniFocus projects or projects due for review. Use view=all (default) for status/folder filters, or view=due_for_review for overdue review work.
Takes no parameters.
Example callreturns →
Mark a user-confirmed set of active or on-hold projects reviewed. The complete batch is validated first and review dates are verified afterward.
Takes no parameters.
Example callreturns →
List, get, add, edit, or remove OmniFocus folders. This mixed-operation tool is conservatively marked destructive: list/get are read-only, add/edit mutate, and remove permanently deletes contained projects and tasks.
Takes no parameters.
Example callreturns →
Append text to a task or project note without overwriting the existing note. Useful for logging progress or adding context.
Takes no parameters.
Example callreturns →
Count tasks matching filters without returning the full list. Fast
Takes no parameters.
Example callreturns →
Duplicate an existing task, optionally with its subtasks, and optionally with a new name. Useful for template-based workflows.
Takes no parameters.
Example callreturns →
List, add, or remove task notifications. This mixed-operation tool is conservatively marked destructive: list is read-only, add mutates, and remove deletes one or all notifications.
Takes no parameters.
Example callreturns →
Startermost installed
$12 / month
- 10,000 calls a month, included
- 120 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Team
$39 / month
- 50,000 calls a month, included
- 600 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Scale
$89 / month
- 250,000 calls a month, included
- 3,000 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $12 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 93 / 100
Release 2.2.0 · scanned 25 Aug 2026
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.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digeste0ba3a3df8669e469a4237622bbb45c5329419d7c70086aeacddc3f1eb89d6ce
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
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
Integrityfirst-seen
Surface digeste0ba3a3df8669e46
Scanned2026-08-25
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
Pinned to 2.2.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
2.2.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Omnifocus Mcp Enhanced in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
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 an account with 50 real tool calls against it.