OmniFocus MCP Server

Created By
themotionmachinea year ago
Claude's OmniFocus integration: Let LLMs interface with your tasks through the Model Context Protocol. Add, organize, and query your OmniFocus database with natural language commands.
Overview

What is OmniFocus MCP?

OmniFocus MCP is a Model Context Protocol (MCP) server that allows integration with OmniFocus, enabling users to interact with their tasks and projects using natural language commands.

How to use OmniFocus MCP?

To use OmniFocus MCP, set up the server and send JSON commands to add, organize, and query tasks in your OmniFocus database.

Key features of OmniFocus MCP?

  • Add new tasks to OmniFocus with detailed attributes.
  • Organize tasks by project and tags.
  • Query tasks using natural language commands.

Use cases of OmniFocus MCP?

  1. Automating task management in OmniFocus.
  2. Integrating with AI to manage tasks through voice commands.
  3. Enhancing productivity by organizing tasks efficiently.

FAQ from OmniFocus MCP?

  • Is OmniFocus MCP ready for production use?

No, it is currently a work in progress and not yet ready for serious use.

  • What programming language is OmniFocus MCP built with?

OmniFocus MCP is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
themotionmachine
Star
16
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago