An MCP server is the difference between an AI that talks about your Mac and an AI that uses it. Claude Code can explain how to file a reminder, screenshot a window, or rerun a failing test. Wire in the right MCP server and it does those things instead.
Finding servers isn't the hard part in 2026. There are thousands, and most ranked lists recycle the same dozen without checking whether anyone still maintains them. We checked. Every star count, version, and maintenance status below was verified against the GitHub API on June 9, 2026, and one server that other lists still recommend turned out to be archived.
Last updated June 2026. Stars and release dates verified June 9, 2026.
What are the best MCP servers for Mac in 2026?
The best macOS MCP servers in 2026 are ToolPiper (300+ native tools across 26 Mac domains, free, one install), XcodeBuildMCP (Xcode builds, tests, and simulators), Peekaboo (screenshots and GUI automation), Desktop Commander (terminal and files), and Playwright MCP (browser automation). Apple's own xcrun mcpbridge, new in Xcode 26.3, covers IDE-level tooling.
We weighted three things. How much of the Mac a server actually reaches, whether a named publisher is still shipping releases, and how much runtime you have to install before the first tool call. The picks are grouped by job, because the best server depends on what you're handing the agent.
The landscape moved this year. Apple shipped its first MCP server in February, Sentry bought the most popular Xcode server, and the most-recommended Apple-apps server quietly went read-only. A list written in 2025 is wrong in at least three places by now, which is most lists.
Controlling the Mac itself
1. ToolPiper
Our app, so judge the claims rather than the placement. ToolPiper is the only entry on this list that's a full native macOS app instead of a Node or Python process. One install serves over 300 MCP tools across 26 macOS domains - clipboard, calendar, screenshots, audio, files, browser automation through 14 AX-native CDP tools, and 142 system actions for windows, apps, and settings. No Docker, no Python, no Node. Free, no account.
One command wires it into Claude Code, and the setup guide walks through it. ToolPiper is also an MCP client, so it can consume other servers on this list. And the server is one face of a larger app - the same install runs local models, voice, and a visual pipeline builder. The full catalog is in the MCP server overview.
The honest limits. macOS only, and the browser tools drive Chrome over CDP, not Safari or Firefox. If you need one of the narrower servers below, nothing stops you from running it alongside.
2. Peekaboo
Peter Steinberger's screen automation server, now under the openclaw org. The agent sees the screen, clicks, types, scrolls, and walks menu bars through accessibility actions. 4,677 stars, MIT, and the cadence is fast - v3.4.0 shipped June 7, 2026. Install with npx -y @steipete/peekaboo, grant Screen Recording and Accessibility permissions, macOS 15 or later. Source at github.com/openclaw/Peekaboo.
It ranks this high because see-and-click is the capability that makes everything else composable. When an app has no dedicated server and no AppleScript dictionary, GUI automation still works.
3. iMCP
Mattt Thompson's menu-bar app covers the personal-data side of the Mac. Calendar, Contacts, Messages, Reminders, Location, and Weather, reached through the real EventKit and Contacts frameworks so macOS permission prompts do the gatekeeping. 1,450 stars, MIT, maintained, at github.com/mattt/iMCP.
This is also where the correction goes. The server most lists still recommend for this job, apple-mcp from supermemoryai (3,114 stars), has been archived and read-only since August 2025. Nobody is patching it. iMCP is the maintained pick for Messages and Calendar access, and ToolPiper covers the same domains as part of its catalog.
4. macos-automator-mcp
Steinberger again. This one runs arbitrary AppleScript and JXA and ships 200+ prebuilt recipes for common apps. 816 stars, MIT, pushed in June 2026, at github.com/steipete/macos-automator-mcp. It's the escape hatch - when nothing else reaches an app, AppleScript usually does. The same property makes it the entry to scope most carefully, because arbitrary script execution is exactly what it sounds like.
For Apple developers
5. XcodeBuildMCP
The Xcode toolchain server. Builds, tests, simulators, physical devices, and logs, driven headlessly through xcodebuild. Cameron Cooke built it, Sentry acquired it, and Sentry keeps shipping - v2.6.2 landed June 2, 2026. 5,878 stars, MIT, installed with npx xcodebuildmcp@latest, at github.com/getsentry/XcodeBuildMCP. If an agent writes Swift on your machine, this is what lets it verify its own work.
6. Apple's xcrun mcpbridge
Apple shipped its first MCP server in Xcode 26.3 in February 2026. xcrun mcpbridge exposes roughly 20 tools XPC-bridged into a running Xcode instance - project structure, builds, tests, diagnostics - and the Xcode 27 beta from WWDC June 2026 adds debugger tools. Closed source, ships with Xcode, enabled under Xcode Settings, Intelligence pane.
It pairs with XcodeBuildMCP rather than replacing it. mcpbridge needs the IDE open and reflects its live state. XcodeBuildMCP drives xcodebuild headlessly with no IDE in sight. CI-shaped work wants the second, in-editor context wants the first. Apple is extending MCP further in the OS 27 cycle per WWDC 2026 coverage, but Apple hasn't confirmed a system-level MCP client in macOS 27 as of June 2026, so treat anything beyond Xcode as unannounced.
7. Desktop Commander
Eduard Ruzga's terminal and filesystem server, and the most-starred standalone entry in this group at 6,138. The agent gets a real shell with long-running process support (your dev server survives between tool calls), plus file reads, writes, and surgical diff-based edits. MIT, actively maintained as of June 2026. Setup is npx @wonderwhy-er/desktop-commander@latest setup, source at github.com/wonderwhy-er/DesktopCommanderMCP. Terminal control is everything control, so scope it deliberately and read the security section below.
8. iterm-mcp
Ferris Lucas's server takes a different angle - it shares the iTerm2 session you already have open, so you watch every command as it runs and can step in mid-stream. 560 stars, MIT, at github.com/ferrislucas/iterm-mcp. The caveat that drops it to the bottom of the group is maintenance. The last push was September 2025. It still works, but nine months of silence means you should test it against current clients before relying on it.
Browser automation
9. Playwright MCP
Microsoft's server is the biggest project on this list at 33,700 stars, Apache-2.0, and very active. It drives browsers through accessibility-tree snapshots rather than screenshots, which keeps responses structured and cheap in tokens. Install with npx @playwright/mcp@latest, source at github.com/microsoft/playwright-mcp. Cross-platform, huge community, the default answer for web work.
Where it stops - driving the browser is all it does. No assertion tools, no test persistence, no export, and the full accessibility snapshot it returns on every interaction adds up in long sessions. If the goal is tests rather than browsing, we compared it against ToolPiper's 20 browser-testing tools in our MCP testing breakdown. For plain web automation across platforms, take the Microsoft server and don't overthink it.
Files, notes, and tasks
10. Filesystem (Anthropic reference server)
The reference implementation from the modelcontextprotocol/servers monorepo, which sits at 86,977 stars. Directory-scoped file access - the agent reads and writes only inside directories you name at launch, with npx -y @modelcontextprotocol/server-filesystem ~/Projects. Source at github.com/modelcontextprotocol/servers. Boring in the best way, and the scoping model is the part worth copying. Explicit allow-listed directories beat access-to-everything every time.
11. mcp-obsidian
Markus Pfundstein's bridge into an Obsidian vault through the community Local REST API plugin. The agent searches, reads, and writes notes while Obsidian keeps owning the storage. 3,876 stars, MIT, maintained, at github.com/MarkusPfundstein/mcp-obsidian. Installing the plugin first is one more moving part than anything else here, but this is the most-used path between agents and Obsidian.
12. things-mcp
Alex Hald's server for Things 3. Small and focused. The agent reads your lists and adds tasks, and that's the whole job. 497 stars, MIT, maintained, at github.com/hald/things-mcp. At this scope, small is a feature.
How the twelve compare
One table, the facts that decide an install. Star counts are in the entries above and were read from the GitHub API on June 9, 2026.
How do you choose an MCP server?
Choose by job. ToolPiper for broad Mac control from one install, XcodeBuildMCP plus Apple's mcpbridge for Xcode work, Playwright MCP for web apps, and the directory-scoped Filesystem server for file access. Prefer maintained servers from named publishers, and grant each one the narrowest permissions it needs.
Two more filters earn their keep. Count the runtimes first. Every npx server drags Node into the path of your AI agent, Python servers add uv or pip, and the totals creep. Three servers can mean three runtimes plus config blocks in every MCP client you use. Native apps like ToolPiper and iMCP skip that tax entirely.
Then count the tools. Every connected server loads its tool definitions into the agent's context window before any work happens, so a pile of narrow servers can cost more tokens per session than one broad one, and some clients get worse at picking the right tool as the registry grows. Start with the single server that covers your main job and add the second when the agent actually hits a wall.
And check the maintenance date before you wire anything in. Half the value of this list is the verification work, and that work expires. A server that shipped a release this month will probably survive the next protocol revision. One that's been quiet since last fall might not.
Are MCP servers safe to run?
MCP servers run with your user account's permissions, and security roundups counted more than 30 CVEs filed against MCP servers in January and February 2026. Prefer maintained servers from named publishers, scope filesystem and terminal access to specific directories, and treat each new server as software you're installing, because it is.
That CVE wave was predictable. MCP servers are young code with broad permissions, and plenty were weekend projects that hit ten thousand stars before anyone audited them. Maintenance status is your best proxy for whether the next disclosure gets patched, which is why this list flags the archived and the slow-moving instead of pretending stars equal safety.
The practical rules are short. Run servers from publishers with names and track records. Give filesystem and terminal servers explicit directory scopes, not your home folder. Treat macOS permission prompts for Screen Recording, Accessibility, and Automation as the real gate they are - a native server that asks through the system is showing you its scope, which is more than a generic Node process can say. And anything that executes arbitrary scripts (Desktop Commander, macos-automator-mcp, iterm-mcp) deserves the same trust decision as handing someone your keyboard.
If you want the broadest Mac control for the least setup, start with ToolPiper. One install, 300+ tools, free, and the MCP page lists everything it serves. Download it at modelpiper.com/download.
Publishing alongside this list: what AI agents can actually do on a Mac once the tools are wired in.