Macos MCP Server vs Mobilerun
A side-by-side look at the Macos MCP Server and Mobilerun MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Macos MCP Server for os automation work as a local process; choose Mobilerun for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Macos MCP Server when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
macos_get_info, macos_check_permissions, macos_manage_apps.
Choose Mobilerun when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 57/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 9,760 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 13 | Not listed |
| Full listing | View Macos MCP Server | View Mobilerun |
Tools & capabilities
Macos MCP Server tools 13
macos_get_infoSystem snapshot: battery level and charging status, power source, Wi-Fi association and network name, hostname, macOS version, uptime, and display count; a failed probe leaves its field null and named in `unavailablemacos_check_permissionsReports Accessibility, Screen Recording, and Automation > Finder status for the calling process from Apple's prompt-free checks — null with a reason when a check can't tellmacos_manage_appsList running apps, get the frontmost app, launch, quit, force-quit, hide, or show applicationsmacos_manage_windowsList, focus, move, resize, move_resize, minimize, fullscreen, or close windows across all visible appsmacos_control_volumeGet or set system output volume (0–100) and mute statemacos_control_audioList audio devices, get current defaults, or switch the default input/output devicemacos_control_appearanceGet or set dark/light modemacos_control_systemLock the screen or put the display to sleepmacos_take_screenshotCapture the main display, one display by `display_index`, a named app window, or a pixel region; saves a PNG without replacing existing files unless `overwrite` is true, optional JPEG previewmacos_manage_displaysList connected displays (with each one's `index`) and the configured layout names, and apply a named display layout presetmacos_send_notificationPost a notification to macOS Notification Centermacos_manage_focusGet or set Do Not Disturb / Focus mode- +1 more on the listing page
Mobilerun tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Macos MCP Server
{
"mcpServers": {
"macos-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/macos-mcp-server"
]
}
}
}
Mobilerun
{
"mcpServers": {
"mobilerun": {
"command": "uvx",
"args": [
"mobilerun"
]
}
}
}
Frequently asked questions
Macos MCP Server is categorized under OS Automation and uses a local stdio subprocess. Mobilerun belongs to OS Automation and uses a local stdio subprocess. Pick Macos MCP Server for os automation work and Mobilerun for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Macos MCP Server has no declared pricing — check the project's own site. Mobilerun has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add macos-mcp-server and mobilerun as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Macos MCP Server has a quality signal of 57/100 (Good) with 0 views, 0 installs and 4 GitHub stars. Mobilerun has 49/100 (Fair) with 8 views, 0 installs and 9,760 GitHub stars.