Macos MCP Server vs Agent Device

A side-by-side look at the Macos MCP Server and Agent Device MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Macos MCP Server logoMacos MCP ServerOS Automation · Local subprocess (stdio)Control macOS system settings, apps, windows, audio, displays, screenshots, and Focus mode via MCP.57GoodAuth: not declaredAgent Device logoAgent DeviceOS AutomationDiscovery router for the agent-device CLI. Exposes status, install guidance, version-matched help, prompts, and resources for iOS, Android, tvOS, macOS, and Linux automation workflows.53GoodAuth: no auth required

Verdict: choose Macos MCP Server for os automation work as a local process; choose Agent Device for os automation. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Macos MCP Server logoChoose 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.
Explore Macos MCP Server

Agent Device logoChoose Agent Device when

  • You need dedicated capabilities in the OS Automation domain.
  • Its auth model fits you: No auth required.
Explore Agent Device

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMacos MCP Server logoMacos MCP ServerAgent Device logoAgent Device
CategoryOS AutomationOS Automation
Quality signal57/100 · Good53/100 · Good
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars45,133
Directory activity 0 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools13Not listed

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 `unavailable
  • macos_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 tell
  • macos_manage_appsList running apps, get the frontmost app, launch, quit, force-quit, hide, or show applications
  • macos_manage_windowsList, focus, move, resize, move_resize, minimize, fullscreen, or close windows across all visible apps
  • macos_control_volumeGet or set system output volume (0–100) and mute state
  • macos_control_audioList audio devices, get current defaults, or switch the default input/output device
  • macos_control_appearanceGet or set dark/light mode
  • macos_control_systemLock the screen or put the display to sleep
  • macos_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 preview
  • macos_manage_displaysList connected displays (with each one's `index`) and the configured layout names, and apply a named display layout preset
  • macos_send_notificationPost a notification to macOS Notification Center
  • macos_manage_focusGet or set Do Not Disturb / Focus mode
  • +1 more on the listing page

Agent Device 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "macos-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/macos-mcp-server"
      ]
    }
  }
}

Agent Device

No confirmed install command for Agent Device yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Macos MCP Server is categorized under OS Automation and uses a local stdio subprocess. Agent Device belongs to OS Automation and uses an install path we have not confirmed yet. Pick Macos MCP Server for os automation work and Agent Device 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. Agent Device has no confirmed install command yet — follow its own setup instructions.

Macos MCP Server has no declared pricing — check the project's own site. Agent Device is listed as free. Auth: no auth required. 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 callstackincubator-agent-device 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. Agent Device has 53/100 (Good) with 5 views, 0 installs and 5,133 GitHub stars.