Mac Control Mcp
Give your coding agent deep native control of your Mac—apps, calendar, voice, browser DOM, and undo—without gluing together a dozen one-off scripts.
Overview
mac-control-mcp is a MCP server for the Build phase that exposes 143 native Swift tools for macOS Accessibility, calendar, voice, browser DOM, and undo automation to AI agents.
What is this MCP server?
- 143 native Swift MCP tools covering Accessibility (AX), EventKit, voice, browser DOM, and undo flows
- stdio transport with mcpb package distribution (v0.8.1) for Claude Code, Cursor, and other MCP clients
- Unified macOS automation instead of separate AppleScript, shell, and browser-driver hacks
- Undo-capable actions reduce risk when agents drive UI and calendar changes on your machine
- Targets solo builders who live on a Mac and want the agent to operate their actual desktop environment
- 143 advertised MCP tools
- Server version 0.8.1
- Transport: stdio
Community signal: 15 GitHub stars.
What problem does it solve?
Agents can edit code but cannot reliably operate your Mac’s apps, calendar, or browser without a large, fragile patchwork of scripts.
Who is it for?
Solo builders on macOS who want Claude Code or Cursor to automate real desktop and browser tasks during product and agent workflow development.
Skip if: Teams on Linux-only or headless CI with no Mac workstation, or anyone who only needs in-repo file edits.
What do I get? / Deliverables
After registration, your agent can drive macOS and browser UI through one MCP surface with undo-aware operations instead of ad hoc automation.
- stdio MCP server exposing 143 macOS and browser automation tools
- Agent-callable UI, calendar, voice, and DOM actions with undo support
- Local desktop control path without separate AppleScript orchestration
Recommended MCP Servers
Journey fit
Desktop and browser automation is primarily wired while you build agent workflows and local dev tooling, not during pure idea research. mac-control-mcp is an MCP integration layer that connects agents to macOS APIs and browser surfaces, which fits the integrations shelf in Build.
How it compares
Native macOS MCP automation server, not a repository skill or cloud-only browser API.
Common Questions / FAQ
Who is Mac Control Mcp for?
It is for indie developers and agent builders on Mac who want MCP clients to control UI, calendars, voice, and browser DOM locally.
When should I use Mac Control Mcp?
Use it when you are building agent integrations that must act on macOS apps or browsers on your machine, not just generate code in the repo.
How do I add Mac Control Mcp to my agent?
Install the v0.8.1 mcpb package from the GitHub release, add a stdio MCP server entry pointing at Mac Control Mcp in Claude Code, Cursor, or another MCP host, then grant macOS Accessibility and related permissions.