OmniFocus MCP Server
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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_active_tasksA | Call this tool to get a list of all active (uncompleted) tasks from the user's OmniFocus. Use it when the user asks for their 'active tasks', 'current tasks', or 'open tasks'. |
| get_all_tasksA | Call this tool to get a list of all tasks from OmniFocus, including completed ones. Use it when the user explicitly asks for 'all tasks' or 'completed tasks'. |
| get_active_projectsA | Call this tool to get a list of all active (not completed or dropped) projects from OmniFocus. Use it when the user asks for their 'active projects' or 'current projects'. |
| get_all_projectsA | Call this tool to get a list of all projects from OmniFocus, including completed and dropped ones. Use it when the user explicitly asks for 'all projects'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_active_projects vs. get_all_projects differentiate by completion status, and similarly for tasks. The descriptions explicitly clarify when to use each tool, eliminating any potential for misselection.
All tool names follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (e.g., active_projects, all_tasks). There are no deviations in naming style, making the set predictable and easy to understand.
Four tools are reasonable for a basic OmniFocus integration, covering core read operations for projects and tasks. However, the scope feels slightly thin as it lacks update, create, or delete capabilities, which might be expected for a task management system.
The tool set is severely incomplete for OmniFocus functionality. It only provides read operations for projects and tasks, with no ability to create, update, delete, or manage other entities like contexts, tags, or due dates. This will cause significant agent failures in handling typical task management workflows.