Omnifocus MCP Server

Omnifocus MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Omnifocus MCP directly instead of describing what you should do. MCP server for OmniFocus integration using Omni Automation.

What you get

A Model Context Protocol (MCP) server for integrating OmniFocus with Claude Desktop. This server provides Claude with access to your OmniFocus tasks and projects, enabling AI-powered task management and weekly reviews.

• 🎯 OmniFocus Integration - Access tasks and projects from OmniFocus
• 🔧 Active Task Filtering - Get only uncompleted tasks, excluding templates and system items
• 🚀 TypeScript + MCP SDK - Type-safe and maintainable
• 🔒 Secure Automation - Uses official Omni Automation JavaScript API
• 📱 Claude Desktop Ready - Works seamlessly with Claude Desktop

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Omnifocus MCP is connected, these are the calls the assistant has available:

• Building — The Building tool exposed by this server
• Testing — The Testing tool exposed by this server

Configuration and credentials

• macOS with OmniFocus installed - Node.js 23.10.0 or higher - Claude Desktop application - Automation permissions for OmniFocus

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the omnifocus mcp mcp server does with a few real requests.

Choosing this one

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Omnifocus MCP's toolset — Building, Testing — is a fair guide to whether it matches your workflow. It is maintained by mdoel; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.