Macos Mcp Server
Let Claude Code or Cursor drive your Mac—apps, windows, audio, displays, screenshots, and Focus mode—without you context-switching to System Settings.
Overview
io.github.cyanheads/macos-mcp-server is a Build-phase MCP server that lets coding agents control macOS settings, apps, windows, audio, displays, screenshots, and Focus mode over stdio.
What is this MCP server?
- Stdio MCP package @cyanheads/macos-mcp-server v0.1.3 via npm run start:stdio
- System control: settings, apps, windows, audio, displays, and Focus mode
- Screenshots with configurable MACOS_SCREENSHOT_DIR (defaults to ~/Desktop)
- Named display layouts via MACOS_DISPLAY_LAYOUTS JSON for apply_layout
- MCP_LOG_LEVEL for debug through error observability
- Server version 0.1.3
- npm package @cyanheads/macos-macos-mcp-server with stdio via run start:stdio
- Env vars: MACOS_SCREENSHOT_DIR, MACOS_DISPLAY_LAYOUTS (JSON), MCP_LOG_LEVEL
Community signal: 1 GitHub stars.
What problem does it solve?
Agents can edit code but cannot reliably operate your Mac, so you keep alt-tabbing through Settings and display tools while the agent waits.
Who is it for?
Solo Mac developers who want agents to capture screenshots, tweak displays, or manage Focus while building or documenting a product.
Skip if: Linux or Windows-only builders, headless CI-only workflows, or teams that forbid local OS automation for security policy reasons.
What do I get? / Deliverables
After you register the server in your MCP client, the agent can invoke macOS automation tools using your screenshot directory, layout presets, and log level configuration.
- Registered stdio MCP server controlling apps, windows, audio, displays, screenshots, and Focus
- Configurable screenshot output directory and named display layout presets
- Agent-callable macOS system actions without manual Settings navigation
Recommended MCP Servers
Journey fit
MCP servers that extend what your coding agent can touch on the host machine belong on the Build shelf under integrations, where solo builders wire agent tooling to real environments. macOS control is a direct agent↔OS integration: register stdio MCP, set env vars for screenshots and display layouts, and expose desktop automation alongside your repo workflow.
How it compares
Host macOS automation MCP, not a web browser or cloud infrastructure server.
Common Questions / FAQ
Who is macos-mcp-server for?
Indie and solo builders on macOS who use Claude Code, Cursor, or similar MCP clients and want the agent to operate the desktop—not just the repository.
When should I use macos-mcp-server?
Use it during build and ship when you need screenshots, display layouts, audio or Focus changes, or window management driven from agent sessions without manual System Settings trips.
How do I add macos-mcp-server to my agent?
Install @cyanheads/macos-mcp-server from npm, configure stdio with run start:stdio, optionally set MACOS_SCREENSHOT_DIR and MACOS_DISPLAY_LAYOUTS, then add the server entry in your client’s MCP config.