MacOS MCP
Automate native macOS apps through the Accessibility API so your agent can verify menus, sheets, and multi-window flows.
Overview
macOS-MCP is a Ship-phase MCP server that automates native macOS applications through the Accessibility API for AI-driven UI testing.
What is this MCP server?
- macOS-MCP v0.3.6 stdio server published on PyPI as macos-mcp
- Uses the macOS Accessibility API for trustworthy native UI targeting
- Fits agent workflows alongside Claude Code and Cursor on Mac dev machines
- PyPI install with required runtime argument macos-mcp
- Open-source Jeomon/macos-mcp repository
- Version 0.3.6
- Distribution: PyPI package macos-mcp with stdio transport
What problem does it solve?
Without Accessibility-backed MCP tools, Mac indie developers re-click through the same menu and sheet flows while agents stay blind to native UI.
Who is it for?
Solo builders on macOS shipping native or hybrid desktop apps who want stdio MCP desktop automation without custom AX Swift code.
Skip if: Windows/Linux-only pipelines, iOS simulator-only testing, or teams blocked from granting Accessibility access on managed Macs.
What do I get? / Deliverables
Once Accessibility permissions and the PyPI server are in place, your agent can query and drive macOS UI during test passes on your dev Mac.
- Running stdio macos-mcp server wired into your agent
- Accessibility-driven UI inspection and automation hooks
- Repeatable Mac desktop test assistance before release
Recommended MCP Servers
Journey fit
macOS desktop verification is part of shipping confidently when your product is a Mac app, menu bar utility, or Electron shell on Apple silicon. Accessibility-driven control and inspection map directly to manual and agent-assisted UI testing before launch.
How it compares
macOS Accessibility MCP server, not Windows UI Automation (mcp-test-utils) or browser Playwright tooling.
Common Questions / FAQ
Who is MacOS MCP for?
It is for Mac-based indie developers and agent users who need to automate or inspect native macOS application UI during ship and test work.
When should I use MacOS MCP?
Use it while shipping Mac desktop software when you want an agent to navigate Accessibility trees, trigger controls, and validate multi-window behavior.
How do I add MacOS MCP to my agent?
Install the macos-mcp PyPI package (v0.3.6), run the macos-mcp stdio command, enable Accessibility for your terminal or agent host, and register the server in your MCP client.