pymnifocus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
OmniFocus MCP server for macOS task management.
TOOL GUIDANCE:
Prefer query_omnifocus over dump_database for targeted lookups (85-95% context savings)
Use the "fields" parameter to request only needed fields
Use "summary: true" for quick counts without full data
For batch operations, prefer batch_add_items/batch_remove_items over repeated single calls
RESOURCES:
omnifocus://inbox — current inbox items
omnifocus://today — today's agenda (due, planned, overdue)
omnifocus://flagged — all flagged items
omnifocus://stats — quick database statistics
omnifocus://project/{name} — tasks in a specific project
omnifocus://perspective/{name} — items in a named perspective
QUERY FILTER TIPS:
Task field for tag labels is tagNames (not tags); filters use the tags key for exact tag name(s)
completedAfter / completedBefore accept ISO dates (YYYY-MM-DD) or datetimes; date-only completedBefore is exclusive (tasks completed before that calendar day in local time). Use include_completed true when querying completed work.
Tags filter is case-sensitive and exact match
projectName filter is case-insensitive partial match
Status values for tasks: Next, Available, Blocked, DueSoon, Overdue
Status values for projects: Active, OnHold, Done, Dropped
Combine filters with AND logic; within arrays, OR logic applies
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dump_databaseC | Get the complete current state of your OmniFocus database. Best for comprehensive analysis. |
| query_omnifocusA | Efficiently query OmniFocus database with filters. Get specific tasks, projects, or folders. Task filters include completedAfter and completedBefore (ISO date or datetime, local timezone) to restrict by completionDate; set include_completed true or completed tasks are excluded first. |
| add_omnifocus_taskC | Add a new task to OmniFocus. |
| add_projectC | Add a new project to OmniFocus. |
| remove_itemA | Remove a task or project from OmniFocus. Provide either id or name. |
| edit_itemC | Edit a task or project in OmniFocus. |
| batch_add_itemsB | Add multiple tasks or projects in a single operation (max 100). |
| batch_remove_itemsB | Remove multiple tasks or projects in a single operation (max 100). |
| list_perspectivesB | List all available perspectives in OmniFocus. |
| get_perspective_viewC | Get items visible in a specific OmniFocus perspective. |
| list_tagsB | List all tags in OmniFocus with their hierarchy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_inbox | Current OmniFocus inbox items. |
| resource_today | Today's agenda: due today, planned today, overdue. |
| resource_flagged | All flagged OmniFocus items. |
| resource_stats | Quick OmniFocus database statistics. |
TDQS
Scored across 11 tools
Each tool targets a distinct operation: adding, editing, removing, querying, listing tags/perspectives, etc. The batch variants are clearly separated from single-item operations, and the query/dump tools serve different analytical needs.
Most tools follow a clear verb_noun pattern such as add_project, remove_item, list_tags. Minor deviations like dump_database and query_omnifocus use different prefixes, but the overall style remains readable and predictable.
11 tools is well-scoped for an OmniFocus MCP server, covering CRUD operations, batch operations, querying, and viewing perspectives/tags. The count feels balanced and not excessive for the domain.
Core lifecycle operations are covered (add, edit, remove, batch, query), along with supporting features like tags and perspectives. Minor gaps exist, such as no explicit 'complete task' tool, but these can be handled via edit_item or query filters.