Connects AI assistants to native Mac apps via local MCP server.
What it does
Runs a local MCP server that exposes native macOS applications to connected AI assistants.
Enables AI agents to manage Calendar events, read or draft emails, and handle Notes and Reminders.
Executes Computer Use automation to interact with non-API desktop interfaces via system accessibility controls.
Applies macOS system-level permissions and per-app authorization gates for explicit control over sensitive data.
Why it works
Local-first processing ensures sensitive Mac app data remains on-device during execution.
Standardized MCP protocol allows one Macuse setup to serve multiple AI clients simultaneously.
Computer Use fallback allows automation of legacy desktop software lacking open API access.
Explicit per-app permission model ensures actions require user confirmation rather than universal access.
Connects AI assistants to native Mac apps via local MCP server.
Overview
Macuse is a native macOS application that functions as a local Model Context Protocol (MCP) server, bridging AI assistants directly to desktop applications. By connecting clients such as Claude, Codex, Cursor, and Raycast, Macuse grants AI agents local access to manage macOS Calendar, Mail, Notes, Reminders, Messages, and Contacts. It incorporates Computer Use automation to click, scroll, and type inside apps lacking public APIs, executing desktop tasks while keeping user data processed locally on-device.
Founded year:2026
Founder:Yuexun Jiang
Team size:1
Popularity:Used by early adopter developers on Product Hunt with 120+ upvotes and 120+ followers.
Integrations:Apple Calendar, Apple Mail, Apple Notes, Apple Reminders, Apple Messages, Apple Contacts, Shortcuts, Maps, Claude, Codex, Cursor, Raycast, Model Context Protocol (MCP)
What it does
Runs a local MCP server that exposes native macOS applications to connected AI assistants.
Enables AI agents to manage Calendar events, read or draft emails, and handle Notes and Reminders.
Executes Computer Use automation to interact with non-API desktop interfaces via system accessibility controls.
Applies macOS system-level permissions and per-app authorization gates for explicit control over sensitive data.
Who it's for
macOS Power Users & Productivity Enthusiasts
Developers Building MCP-Compatible AI Agents
Knowledge Workers Managing Desktop Workflows
AI Engineers Utilizing Computer Use Automation
Why it works
Local-first processing ensures sensitive Mac app data remains on-device during execution.
Standardized MCP protocol allows one Macuse setup to serve multiple AI clients simultaneously.
Computer Use fallback allows automation of legacy desktop software lacking open API access.
Explicit per-app permission model ensures actions require user confirmation rather than universal access.
Founder story
Macuse was created in 2026 by Sydney-based full-stack engineer Yuexun Jiang (creator of Badgeify and former engineer at Tencent and Alibaba). Observing that AI reasoning models frequently hit a wall on macOS because they could not directly interact with local calendars, mail, or notes, Jiang developed Macuse as a local MCP server to give AI models permissioned access to native Mac tools.
Alternatives
Comparison overview
Macuse acts as a local MCP server exposing native macOS apps directly to external LLM clients, whereas standard AI desktop tools operate as self-contained chatbots without deep local app controls.
Macuse combines native Apple app API integrations with Computer Use accessibility automation, whereas conventional automation utilities rely exclusively on web scraping or explicit webhooks.