Best macOS MCP servers for GUI automation in 2026: an honest roundup
Eight MCP servers that let AI agents operate Mac apps, free and paid, compared on background use, several agents, clipboard, setup and license, each checked against its own docs.
Short answer: For free, open-source GUI automation on a Mac, start with Cua Driver or Peekaboo. Both are MIT licensed and document background input for many apps; Cua Driver also runs on Windows and Linux. computer-use-mcp is a smaller MIT option with a visible agent cursor, and Macuse adds Calendar, Mail and Notes integrations with a free daily quota. Servers built on PyAutoGUI drive the real pointer. ShadowCursor is the paid option that gives every agent its own cursor, keyboard and clipboard, with several agents at once.
How this roundup was made
Every entry was checked against its own README, documentation or website on 2026-10-20. Where a project does not document something, the table says so instead of guessing. "Background" means the project says input reaches the target app without moving the pointer or bringing the app to the front. No server guarantees that for every app, so test with the apps you actually use.
New to the idea? What a computer use MCP server does explains the basics and the questions to ask before you pick one. This roundup covers servers that operate the graphical interface; for browser-only automation see Playwright MCP vs computer use.
The comparison table
| Server | Background or foreground | Several agents | Clipboard | Setup | License and price |
|---|---|---|---|---|---|
| ShadowCursor | Background, also in covered windows | Several, each with its own cursor, keyboard and clipboard | A private clipboard per agent | Mac app, one-click connection to Claude, Codex, Cursor and VS Code | Commercial: 7-day trial, then $12.99 per month or $69.99 per year |
| Cua Driver | Background by default where app and platform support it | Several sessions, each with a cursor overlay; they share one keyboard and focus | Tools read and replace the system clipboard | Shell installer, permission grant, registration in your client | MIT, free |
| Peekaboo | Background for targeted input; some actions need explicit foreground consent | Not documented | Reads and writes the system clipboard | Homebrew or npx (Node 22+), client configuration | MIT, free |
| Macuse | Background, according to its website | Free plan: one connected client; Lifetime: unlimited | Not documented | Mac app, plugin for Claude Code and Codex, bundle for Claude Desktop | Commercial: 100 tool calls per day free, Lifetime $49 once |
| computer-use-mcp | Background by default; real pointer only as an opt-in fallback | Several sessions through one shared daemon | Read and write tools; separation not documented | Release binary or Swift build, client configuration | MIT, free, pre-1.0 |
| macOS-MCP (CursorTouch) | Not documented; tools move the pointer and type at the cursor | Not documented | No clipboard tool listed | Python 3.11+ with uv, client configuration | MIT, free |
| mcp-server-macos-use (Mediar) | Not documented; opening an app activates it | Not documented | No clipboard tool listed | Swift build, client configuration | Business Source License 1.1 |
| computer-control-mcp | Foreground: PyAutoGUI moves the real mouse and activates windows | One shared pointer | No clipboard tool listed | uvx or pip, client configuration | MIT, free |
Claude Code also ships a built-in computer-use MCP server. It hides your other apps while Claude works, lets one session use the computer at a time and needs a Pro or Max plan (source). The comparison of Claude, Codex and ShadowCursor covers it and the other built-in options.
Cua Driver
Cua Driver is MIT licensed, runs on macOS, Windows and Linux, and connects through MCP, a CLI or SDKs. Its documentation says it "does not raise the window, move the real pointer, or switch the frontmost app", and each session has a visible cursor overlay. Chrome is driven through its own browser tools, including inactive tabs (platform support). For parallel work: "All sessions still share one screen, keyboard, and focus, and native input is admitted one action at a time." Sources: how Cua Driver works, MCP tools. The detailed comparison is in Cua Driver vs ShadowCursor.
Peekaboo
Peekaboo, now under the OpenClaw organization, is an MIT-licensed CLI and menu bar app for macOS 15 or later that exposes its tools to MCP clients. Its strengths are breadth and scripting: capture, inspection, menus, dialogs, the Dock, Spaces and windows, plus a built-in agent for hosted or local models. Targeted input stays in the background when Peekaboo can resolve the target process; key chords without an exact window, drags across windows and human-style movement need explicit foreground consent (automation guide). More in Peekaboo vs ShadowCursor.
Macuse
Macuse is a commercial Mac app with two halves: direct integrations for Calendar, Mail, Notes, Reminders, Messages, Contacts, Maps and Shortcuts, and computer use for any other app, which its website says runs in the background. The free plan allows 100 tool calls per day and one connected client; Lifetime costs $49 once for three devices (pricing). Its README notes that in Codex, write operations currently fail because Codex declines consent prompts from third-party MCP servers.
computer-use-mcp
computer-use-mcp is a single Swift binary for macOS 14 or later, MIT licensed and explicitly pre-1.0. It tries accessibility actions first, then events routed to the target window or process, and moves the real pointer only when you allow it per call. A self-drawn agent cursor shows where it acts, and concurrent agents go through one shared daemon with per-app leases, so two agents do not interleave actions inside the same app. Its README lists known limits: some apps that need real keyboard focus ignore background events, and menu shortcuts are unreliable in the background.
Small Python and Swift servers
- macOS-MCP (CursorTouch, MIT, Python 3.11+, macOS 12 or later) reads the accessibility tree and offers click, type, scroll, pointer moves, shortcuts, window management and a shell tool that runs commands and AppleScript. Clicks go to coordinates and typing goes to the cursor position; background operation is not documented. The shell tool reaches far beyond the GUI, so treat it like terminal access.
- mcp-server-macos-use (Mediar) is a Swift server that opens or activates an app, clicks at coordinates, types and presses keys, and returns the accessibility tree after each step. Its license is the Business Source License 1.1, which limits production use, and you build it yourself.
- computer-control-mcp (MIT) is built on PyAutoGUI with OCR. It moves the mouse cursor, types at the current cursor position and brings windows to the foreground, so the agent and you share one pointer. It is quick to try with
uvxand is not specific to the Mac.
ShadowCursor
ShadowCursor is a Mac app and MCP server. Every connected agent gets its own cursor, drawn in its color with a name tag, its own keyboard whose keys arrive only in its window, its own clipboard, and its own windows, which it works in even when yours cover them. Several agents can work at once, input moves like a person (curved paths, typing at about 200 words per minute), and Claude, Codex, Cursor and VS Code connect with one click.
Its limits: it needs macOS 15 or later (Windows 10 and 11 are in beta) and has no free tier. Minimized and hidden windows cannot be operated, system drag and drop of files, tabs or text is cancelled, hover without a click works in Safari but not in Chrome or Electron apps, and an agent opens its own browser window instead of using a background tab of yours.
Which one to pick
- Free and open source, comfortable with a terminal: Cua Driver if you also need Windows, Linux or VMs; Peekaboo if you want a Mac CLI you can also script without an AI client.
- Mostly Calendar, Mail, Notes and Reminders: Macuse's direct integrations skip the clicking.
- A small codebase to read and extend: computer-use-mcp or macOS-MCP.
- The agent may have the Mac to itself while it works: a PyAutoGUI server is enough and the simplest to understand.
- Claude Code on Pro or Max, one session at a time: the built-in
computer-useserver may be all you need. - Several agents at once, each with its own cursor, keyboard and clipboard: ShadowCursor.
Before you grant permissions to any of them, read whether it is safe to let an AI agent control your Mac.
FAQ
What is the best free MCP server for macOS?
For GUI automation, Cua Driver and Peekaboo are the strongest free options. Both are MIT licensed, document background input for many apps and connect to Claude Code, Codex and Cursor. Cua Driver also runs on Windows and Linux; Peekaboo is Mac only and adds a scriptable CLI.
Which macOS MCP servers work in the background?
Cua Driver, Peekaboo (for targeted input), computer-use-mcp, Macuse (according to its website) and ShadowCursor document background operation. Servers based on PyAutoGUI drive the real pointer. With every server, some apps only accept input when they are in front.
Can several AI agents share one macOS MCP server?
It depends on the server. computer-use-mcp routes concurrent sessions through one daemon with per-app leases. Cua Driver gives each session its own cursor overlay, but sessions share one keyboard and focus and act one at a time. ShadowCursor gives each agent its own cursor, keyboard and clipboard. For the others it is not documented. Running several AI agents at once explains why this matters.
Do I need one of these if I only automate websites?
Often not. A browser automation server such as Playwright MCP is faster and more precise for web pages. A computer use server is for native apps, system dialogs and desktop software; Playwright MCP vs computer use explains where the line is.
What permissions do these servers need?
Expect to grant Accessibility and Screen Recording to any of them; Peekaboo also uses Event Synthesizing for background keys. Servers launched through Python or uv, such as macOS-MCP, need them granted to your terminal and interpreter.