OmniFocus MCP Server
A Model Context Protocol server that integrates OmniFocus with Claude Desktop, providing AI-powered access to tasks and projects for enhanced task management and weekly reviews.
Tools
get_active_tasks
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_tasks
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_projects
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_projects
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'.
README
OmniFocus MCP Server
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.
Features
- 🎯 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
Current Tools
omnifocus:get_all_tasks
Retrieve all tasks from OmniFocus with filtering options:
includeCompleted(boolean) - Include completed tasks (default: false)limit(number) - Maximum number of tasks to return (default: 100)
omnifocus:get_active_tasks
Retrieve only active (uncompleted) tasks, automatically filtering out:
- Tasks from "Templates" folders
- Tasks containing template placeholders (
«,») - Tasks with synced preferences markers (
⚙️)
omnifocus:get_projects
Retrieve all active projects from OmniFocus.
Prerequisites
- macOS with OmniFocus installed
- Node.js 23.10.0 or higher
- Claude Desktop application
- Automation permissions for OmniFocus
Installation
-
Clone the repository:
git clone https://github.com/mdoel/omnifocus-mcp cd omnifocus-mcp -
Install dependencies:
npm install -
Build the project:
npm run build -
Configure Claude Desktop:
Add this to your Claude Desktop MCP configuration:
{ "mcpServers": { "omnifocus": { "command": "/path/to/omnifocus/run-server.sh", "args": [] } } }Important: Replace
/path/to/omnifocus/with the actual path to your project directory. -
Grant automation permissions:
The first time you run the server, macOS will prompt you to grant automation permissions for OmniFocus. Click "Allow" when prompted.
Note: If you encounter permission issues, you may need to temporarily uncomment the
osascriptlines inrun-server.shto trigger the permission dialog. After granting permissions, comment those lines out again to avoid the dialog on every startup. -
Restart Claude Desktop to load the new MCP server.
Usage
Once configured, you can ask Claude to:
- "Get all my active tasks from OmniFocus"
- "Show me my projects"
- "What tasks do I have for today?"
- "Help me with my weekly review"
Architecture
Core Components
OmniFocusClient- Handles communication with OmniFocus via Omni AutomationOmniFocusJXA- Utility for building and executing JXA scriptsOmniFocusMCPServer- Main MCP server implementation
Directory Structure
src/
├── index.ts # Main entry point
├── server.ts # MCP server implementation
├── omnifocus/
│ ├── client.ts # OmniFocus automation client
│ └── omnifocus-jxa.ts # JXA script utilities
└── types/
└── omnifocus.ts # TypeScript definitions
Development
Building
# Build the project
npm run build
# Watch mode for development
npm run dev
Testing
You can test the server locally:
# Test with command line arguments
node dist/index.js all # Get all tasks
node dist/index.js active # Get active tasks only
node dist/index.js projects # Get projects only
Testing OmniFocus Automation
Test OmniFocus automation directly:
# Test basic connection
osascript -l JavaScript -e "Application('OmniFocus').running()"
# Test task retrieval
osascript -l JavaScript -e "
const app = Application('OmniFocus');
const doc = app.defaultDocument;
const tasks = doc.flattenedTasks();
console.log('Found ' + tasks.length + ' tasks');
"
Troubleshooting
Server Connection Issues
If Claude Desktop can't connect to the server:
- Check the script path in your Claude Desktop configuration
- Verify permissions - ensure the
run-server.shscript is executable:chmod +x run-server.sh - Check Node.js installation - ensure Node.js 23.10.0+ is installed
- Review logs - check Claude Desktop's MCP server logs for error messages
Permission Issues
If you get automation permission errors:
- Open System Preferences > Security & Privacy > Privacy
- Select Automation from the left sidebar
- Find your terminal/shell and check OmniFocus
- Restart your terminal and try again
OmniFocus Not Found
- Ensure OmniFocus is installed and running
- Verify the app name is "OmniFocus" (not "OmniFocus 3" or something similar)
- Check that OmniFocus is not in the trash or disabled
Performance Issues
If the server is slow or times out:
- The server may take time to process large OmniFocus databases
- Consider using the
limitparameter to reduce the number of tasks returned - Ensure OmniFocus is not performing other operations
Contributing
This project is designed to be extensible. To add new functionality:
- Add new tools in the
src/omnifocus/directory - Update the server to register new tools
- Test thoroughly with your OmniFocus data
- Submit a pull request with clear documentation
License
MIT License - see LICENSE file for details.
Support
For issues and questions:
- Check the troubleshooting section above
- Review the Claude Desktop MCP documentation
- Open an issue in this repository
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.