Mac Use Mcp
Let Claude Code or Cursor drive native macOS UI—menus, apps, and desktop actions—without extra native deps beyond the MCP package.
Overview
Mac Use MCP is a MCP server for the Build phase that exposes 18 zero-dependency tools so agents can automate macOS 13+ desktops over stdio.
What is this MCP server?
- 18 MCP tools for macOS desktop automation
- Zero-dependency install via npm stdio package mac-use-mcp
- Requires macOS 13 or newer
- stdio transport for Claude Code, Cursor, and other MCP hosts
- GitHub source at antbotlab/mac-use-mcp v1.1.1
- macOS 13+ required
- Package version 1.1.1
What problem does it solve?
Agents can edit code and browse the web but often cannot reliably operate your actual Mac apps and system UI during local builds.
Who is it for?
Indie devs on macOS 13+ who want local desktop automation from Claude Code or Cursor without maintaining a separate AppleScript toolchain.
Skip if: Windows or Linux builders, CI-only workflows, or teams that forbid agents from controlling the host OS.
What do I get? / Deliverables
After you register mac-use-mcp in your MCP host, the agent can invoke desktop automation tools on your Mac alongside your normal coding session.
- 18-tool macOS automation surface available to your agent
- Repeatable local desktop workflows without extra native dependencies
- stdio MCP registration in your coding agent config
Recommended MCP Servers
Journey fit
Desktop control is wired into the agent stack during product build when you automate local workflows, not during idea or launch copy work. Fits agent-tooling because it extends the coding agent with OS-level tools rather than shipping app frontend code.
How it compares
Native macOS desktop MCP integration, not a headless browser or cloud VM automation skill.
Common Questions / FAQ
Who is Mac Use MCP for?
Solo and indie builders on macOS who use AI coding agents and need real desktop automation beyond the terminal and browser.
When should I use Mac Use MCP?
Use it during build and agent-tooling setup when you want the agent to drive macOS UI locally, not when you only need in-repo edits or remote APIs.
How do I add Mac Use MCP to my agent?
Add the npm package mac-use-mcp with stdio transport in your MCP client config (Claude Code, Cursor, etc.) on a Mac running macOS 13+.