🚀 OmniFocus MCP Enhanced

🌟 NEW: Native Custom Perspective Access with Hierarchical Display!

Transform OmniFocus into an AI-powered productivity powerhouse with custom perspective support

Enhanced Model Context Protocol (MCP) server for OmniFocus featuring native custom perspective access, hierarchical task display, AI-optimized tool selection, and comprehensive task management.

In plain English: this lets your AI assistant read your OmniFocus data, create tasks/projects, organize subtasks, review perspectives, and help you plan work without you manually jumping between apps.

🌠 Why This Project Exists

OmniFocus is already powerful, but it is still mostly a tool you drive by hand.

The bigger idea behind this project is simple:

• less clicking, more conversation

• less manual cleanup, more AI-assisted planning

• less tool memorization, more natural task management

The goal is not just to expose more OmniFocus commands. The goal is to let you work with OmniFocus like this:

Plan my day.
Clean up my Inbox.
Turn these notes into a project.
Show me what is blocked.
Reorganize these tasks safely.

If that feels natural, this MCP server is doing its job.

Want to see where the project is heading next? See the roadmap.

Related MCP server: OmniFocus MCP Server

🆕 Releases

Full notes for every release are on the Releases page. Current surface: 26 tools (16 with structured output), 6 prompts, 3 resources.

✨ Key Features

🌟 NEW: Native Custom Perspective Access

• 🎯 Direct Integration - Native access to your OmniFocus custom perspectives via Perspective.Custom API

• 🌳 Hierarchical Display - Tree-style task visualization with parent-child relationships

• 🧠 AI-Optimized - Enhanced tool descriptions prevent AI confusion between perspectives and tags

• ⚡ Zero Setup - Works with your existing custom perspectives instantly

🏗️ Complete Task Management

• 🏗️ Complete Subtask Support - Create hierarchical tasks with parent-child relationships

• 🔍 Built-in Perspectives - Access Inbox, Flagged, Forecast, and Tag-based views

• 🚀 Ultimate Task Filter - Advanced filtering beyond OmniFocus native capabilities

• 🎯 Batch Operations - Add/remove multiple tasks efficiently

• 📊 Smart Querying - Find tasks by ID, name, or complex criteria

• 🔄 Full CRUD Operations - Create, read, update, delete tasks and projects

• 📁 Folder Management - Full CRUD for folders with nested hierarchy, move/rename, and content inspection

• 🏷️ Tag Management - Full CRUD for tags with nesting, status control, and fuzzy search

• 🔔 Task Notifications - List, add, and remove reminders (absolute time or relative to due date)

• 💬 MCP Prompts - 6 guided workflows (daily, weekly, inbox processing, project planning, project shaping, task health scan)

• 📡 MCP Resources - 3 live JSON snapshots (inbox, today, active projects)

• 🛠️ Agent Skill - One-command install of a local CLI covering all 26 consolidated tools, to keep AI context usage low

• 📅 Time Management - Due, defer, planned dates, estimates, and scheduling

• 🏷️ Advanced Tagging - Tag-based filtering with exact/partial matching

• 🚫 Mutually Exclusive Tags - Automatically respects exclusive tag groups when applying tags

• 🔁 Repeat Rules - Full OmniFocus 4.7+ repetition support (ICS rules, schedule type, anchor date, catch-up, end date, count)

• 🤖 AI Integration - Seamless Claude AI integration for intelligent workflows

• 🖼️ Attachment-Aware Reads - Surface note attachments and linked files before deciding whether AI should inspect them

📦 Installation

Claude Code

Quick Install (recommended)

# One-line installation
claude mcp add omnifocus-enhanced -- npx -y omnifocus-mcp-enhanced

Alternative methods for Claude Code:

# Upgrade to latest
npm install -g omnifocus-mcp-enhanced@latest

# Global installation
npm install -g omnifocus-mcp-enhanced
claude mcp add omnifocus-enhanced -- omnifocus-mcp-enhanced

# Local project installation (project-scoped)
# This creates/updates the current project's .mcp.json so the server is only available here.
git clone https://github.com/jqlts1/omnifocus-mcp-enhanced.git
cd omnifocus-mcp-enhanced
npm install && npm run build
claude mcp add -s project omnifocus-enhanced -- node "/path/to/omnifocus-mcp-enhanced/dist/server.js"

You can also install from npm into the consuming project's devDependencies instead of cloning:

npm install --save-dev omnifocus-mcp-enhanced
claude mcp add -s project omnifocus-enhanced -- npx -y omnifocus-mcp-enhanced

After adding, run claude once in the project directory and approve the pending MCP connection.

Claude Desktop / Cowork

Add the server to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "omnifocus-enhanced": {
      "command": "npx",
      "args": ["-y", "omnifocus-mcp-enhanced"]
    }
  }
}

For a local clone, use:

{
  "mcpServers": {
    "omnifocus-enhanced": {
      "command": "node",
      "args": ["/path/to/omnifocus-mcp-enhanced/dist/server.js"]
    }
  }
}

Restart Claude Desktop after editing the config file.

Using Both Claude Code and Claude Desktop / Cowork

Claude Code and Claude Desktop read separate configurations. If you want to use this MCP server from both, you need to install it in both places — run claude mcp add for Claude Code and add the entry to claude_desktop_config.json for Claude Desktop / Cowork.

📋 Requirements

• macOS 10.15+ - OmniFocus is macOS-only

• OmniFocus 3+ - The application must be installed and running

• OmniFocus Pro - Required for custom perspectives (new features in v1.6.0)

• Node.js 18+ - For running the MCP server

• Any MCP-capable client - Claude Code, mcporter, or another MCP host

🚦 Start Here

If you only want the fastest way to understand this project, remember this:

1. Connect the MCP server to your AI client.

2. Talk to the AI naturally.

3. Let it read, plan, create, move, or update your OmniFocus tasks for you.

You do not need to memorize all tool names first.

🙋 What This Is Good For

• Daily planning: ask your AI what is due today, what is flagged, and what you can finish in 30 minutes.

• Project setup: give the AI a rough goal, then let it create a project and break it into subtasks.

• Inbox cleanup: ask it to review Inbox tasks and sort them into next actions, projects, or someday/later buckets.

• Perspective reviews: ask it to open one of your custom perspectives and summarize what matters.

• Batch capture: paste meeting notes or a brainstorm list and let the AI create multiple tasks at once.

• Attachment-aware review: let the AI inspect task attachments only when needed.

💬 Example AI Conversations

This is the primary way to use this server. You don't call tools by hand — you talk to your assistant and it picks the tools. These prompts work in Claude Code, Claude Desktop, or any MCP client wired to the same server.

Planning your day

Check my Forecast and flagged tasks, then tell me the 3 most important things to do today.
Prefer tasks that take under 60 minutes first.

Open my custom perspective "今日工作安排" and summarize:
- what is due soon
- what looks blocked
- what I can finish quickly

Clearing the Inbox

Review my Inbox and group the tasks into:
1. do today
2. schedule later
3. turn into projects
Then help me clean up the obvious ones.

Turn these meeting notes into OmniFocus tasks under the project "Website Refresh".
Use subtasks where it makes sense and keep the task names short.

Shaping and editing work

Create a project called "Launch spring newsletter".
Add the main subtasks, estimated minutes, and mark the most important step as flagged.

Everything in "Website Refresh" slipped a week.
Show me the affected tasks first, then push every due date out by 7 days once I confirm.

Make "Weekly finance review" repeat every Monday at 9am,
and add a reminder 30 minutes before it is due.

Reviewing

Which projects are due for review? Walk me through them one at a time,
then mark the ones I confirm as reviewed.

My "Today" perspective is matching far too much.
Show me the filter rules behind it and explain what each one does before changing anything.

Working with attachments

Find the task called "Review design draft".
Show me what attachments it has first.
Only open the image attachment if there is one.

🧭 Practical Usage Tips

• Ask the AI to look first, then change things if you want safer workflows.

• Use task IDs when you have duplicate task names.

• For subtasks, let the parent task determine the project. Do not also pass projectName.

• For mcporter, complex arrays are much more reliable with --args '{...}'.

🎯 Core Capabilities

Runnable examples for every row are in the Cookbook.

🛠️ Complete Tool Reference — 26 Tools

Task and project operations

1. dump_database - Export the OmniFocus database

2. add_omnifocus_task - Create one task, including subtasks and repetition

3. add_project - Create one project

4. remove_item - Delete a task or project

5. edit_item - Edit or reposition a task or project

6. move_task - Move one task

7. batch_move_tasks - Atomically move a confirmed task set

8. batch_complete_tasks - Atomically complete or reopen up to 100 tasks

9. batch_edit_items - Atomically edit fields, tags, and project review cadence on up to 100 tasks or projects, with relative date shifts

10. batch_add_items - Add multiple tasks or projects

11. batch_remove_items - Atomically delete a confirmed item set

12. create_project_from_outline - Create and verify one complete project tree

13. get_task_by_id - Read one task and its attachment metadata

14. read_task_attachment - Read one reported task attachment

15. get_tasks - Read inbox, flagged, forecast, tag, or custom-perspective tasks via source

16. filter_tasks - Filter tasks by status, dates, project, tags, text, and more; use { "completedToday": true } for today's completed work

17. get_projects - Read all projects or use view=due_for_review for projects due for review

18. mark_projects_reviewed - Atomically mark confirmed projects reviewed

19. set_repetition_rule - Set, update, or clear a task repeat rule

Organization and productivity

20. manage_perspectives - list, get, or update custom perspectives and their filter rules

21. manage_folders - list, get, add, edit, or remove folders

22. manage_tags - list, search, add, edit, or remove tags

23. manage_task_notifications - list, add, or remove task reminders

24. append_to_note - Append without overwriting a task/project note

25. count_tasks - Count tasks using the filter engine

26. duplicate_task - Duplicate a task, optionally with subtasks

The four manage_* tools mix reads and writes, so their MCP annotations are deliberately conservative and destructive. list/get/search actions do not mutate; remove actions require the same confirmation discipline as dedicated deletion tools. manage_perspectives never creates or deletes a perspective — OmniFocus exposes no automation API for either — so its only write is an in-place edit.

💬 MCP Prompts (NEW in v1.10.0)

Guided review workflows that pull live OmniFocus data and hand the AI a structured plan of attack. In clients like Claude Desktop these appear as selectable prompts.

📡 MCP Resources (NEW in v1.10.0)

Live JSON snapshots your AI client can read without calling a tool.

🛠️ Agent Skill (NEW in v1.11.0)

With 26 consolidated tools, loading every MCP schema still costs context. The bundled omnifocus-cli skill generates a local CLI so agents can drive OmniFocus through compact shell commands instead.

Install

npx -y omnifocus-mcp-enhanced@latest install-skill

By default, this installs only in the current project:

your-project/
├── .claude/skills/omnifocus-cli/
│   ├── SKILL.md
│   └── bin/omnifocus-enhanced.cjs
└── config/mcporter.json

Use --global only when you intentionally want the skill available in every project:

npx -y omnifocus-mcp-enhanced@latest install-skill --global

The global skill is installed in ~/.claude/skills/omnifocus-cli/, and its MCP server registration is written to the home mcporter configuration.

That single command:

1. Registers the MCP server with mcporter, pinned to the exact package version that shipped the installer, with lifecycle: "keep-alive" so repeat calls reuse one warm server instead of cold starting one each time

2. Generates a standalone CLI from the server's live tool schemas (~20s), pinned to the Node runtime so the CLI stays runnable from any shell

3. Installs SKILL.md + the CLI into the current project's .claude/skills/omnifocus-cli/ (or ~/.claude/skills/omnifocus-cli/ with --global)

4. Verifies all 26 tools are present, that keep-alive reached the generated bundle, and that OmniFocus is reachable

Install elsewhere with CLAUDE_SKILLS_DIR=/custom/path npx -y omnifocus-mcp-enhanced@latest install-skill (AGENT_SKILLS_DIR remains available as a legacy alias).

Why generate the CLI locally?

The CLI is not shipped pre-built. It is generated on your machine from the server version you actually have installed, which means it can never silently lack the newest commands — the most common failure mode for this kind of tooling.

Usage

CLI=.claude/skills/omnifocus-cli/bin/omnifocus-enhanced.cjs

$CLI get-tasks --source inbox
$CLI count-tasks --flagged true
$CLI filter-tasks --task-status Available,Next --due-this-week true
$CLI manage-folders --action add --name "Clients" --parent-folder-name "Work"

Flag conventions: booleans need explicit values (--flagged true), arrays are comma-separated (--task-status Available,Next), and --raw '<json>' bypasses flag parsing for complex nested arguments.

Keeping it current

Re-run the installer after upgrading the server — a stale CLI will silently miss new tools:

npm install -g omnifocus-mcp-enhanced@latest
npx -y omnifocus-mcp-enhanced@latest install-skill

install-skill is the only supported refresh path. Do not use mcporter generate-cli --from <bundle>, even though mcporter inspect-cli suggests it: the replay metadata drops the server's lifecycle, so regenerating that way silently disables keep-alive and roughly doubles the latency of every command.

The keep-alive daemon runs against the generated CLI's own config, so a plain mcporter daemon status reads the wrong file and always reports "not running". Inspect the real one with:

npx -y mcporter@latest --config $(ls -t ~/.mcporter/generated/*.json | head -1) daemon status

Batch move feature roadmap (future): docs/roadmap/2026-02-25-batch-move-tasks-plan.md

🚀 Quick Start Examples

Three representative calls. Every tool, every argument, and the full CLI syntax live in the Cookbook.

# Create a task with a project, due date, and planned date
add_omnifocus_task {
  "name": "Review quarterly goals",
  "projectName": "Planning",
  "dueDate": "2025-01-31",
  "plannedDate": "2025-01-28"
}

# Nest a subtask — the parent task determines the project
add_omnifocus_task {
  "name": "Design landing page",
  "parentTaskName": "Launch Product Campaign",
  "estimatedMinutes": 240,
  "flagged": true
}

# Find high-priority work you can actually finish
filter_tasks {
  "flagged": true,
  "taskStatus": ["Available"],
  "estimateMax": 120,
  "hasEstimate": true
}

The Cookbook covers the rest: task moves, custom perspectives, folder and tag management, notifications, repetition rules, batch operations, and attachment inspection.

🔧 Configuration

Claude Code

Verify the server is registered:

# Check MCP status
claude mcp list

# Test basic connection
get_tasks {"source": "inbox"}

# Test custom perspective access
manage_perspectives {"action": "list"}

Claude Desktop / Cowork

Open ~/Library/Application Support/Claude/claude_desktop_config.json and confirm the omnifocus-enhanced entry is present under mcpServers. Restart the app after any changes. Once running, you can test by asking the assistant to list your inbox tasks or custom perspectives.

Troubleshooting

• Ensure OmniFocus 3+ is installed and running

• Verify Node.js 18+ is installed

• For Claude Code: run claude mcp list to confirm the server is registered

• For Claude Desktop / Cowork: verify claude_desktop_config.json is valid JSON and restart the app

• Enable accessibility permissions for terminal apps if needed

🎯 Use Cases

• Project Management - Create detailed project hierarchies with subtasks

• GTD Workflow - Leverage perspectives for Getting Things Done methodology

• Time Blocking - Filter by estimated time for schedule planning

• Review Process - Use custom perspectives for weekly/monthly reviews

• Team Coordination - Batch operations for team task assignment

• AI-Powered Planning - Let Claude analyze and organize your tasks

📈 Performance

• Fast Filtering - Native AppleScript performance

• Batch Efficiency - Single operation for multiple tasks

• Memory Optimized - Minimal resource usage

• Scalable - Handles large task databases efficiently

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

1. Fork the repository

2. Create a feature branch

3. Make your changes

4. Add tests if applicable

5. Submit a pull request

📄 License

MIT License - see LICENSE file for details.

🔗 Links

• NPM Package: https://www.npmjs.com/package/omnifocus-mcp-enhanced

• Cookbook (all CLI/JSON examples): docs/cookbook.md

• GitHub Repository: https://github.com/jqlts1/omnifocus-mcp-enhanced

• OmniFocus: https://www.omnigroup.com/omnifocus/

• Model Context Protocol: https://modelcontextprotocol.io/

• Claude Code: https://docs.anthropic.com/en/docs/claude-code

🙏 Acknowledgments

Based on the original OmniFocus MCP server by themotionmachine. Enhanced with perspective views, advanced filtering, and complete subtask support.

⭐ Star this repo if it helps boost your productivity!