Computer Use vs Mac Use MCP
A side-by-side look at the Computer Use and Mac Use MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Computer Use for os automation work as a local process; choose Mac Use MCP 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 Computer Use when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Choose Mac Use MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
screenshot, get_screen_info, get_cursor_position.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 45/100 · Fair | 53/100 · Good |
| 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 |
Tools & capabilities
Computer Use tools
No tool names declared yet. Check the project README from the listing page.
Mac Use MCP tools 18
screenshotCapture the screen, a region, or a window by title (PNG or JPEG)get_screen_infoGet display count, resolution, origin, and scale factor for each displayget_cursor_positionGet current cursor coordinatesclickClick at screen coordinates with button, click count, and modifier optionsmove_mouseMove the cursor to a positionscrollScroll up, down, left, or right at a positiondragDrag from one point to another over a configurable durationtype_textType text at the cursor position (supports Unicode, CJK, and emoji)press_keyPress a key or key combination (e.g., `"cmd+c"`, `"Return"`)list_windowsList all visible windows with positions and sizesfocus_windowActivate an app and bring a specific window to the frontopen_applicationLaunch an application by name- +6 more on 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.
Computer Use
{
"mcpServers": {
"computer-use": {
"command": "npx",
"args": [
"-y",
"computer-use-mcp"
]
}
}
}
Mac Use MCP
{
"mcpServers": {
"mac-use-mcp": {
"command": "npx",
"args": [
"-y",
"mac-use-mcp"
]
}
}
}
Frequently asked questions
Computer Use is categorized under OS Automation and uses a local stdio subprocess. Mac Use MCP belongs to OS Automation and uses a local stdio subprocess. Pick Computer Use for os automation work and Mac Use MCP 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.
Computer Use has no declared pricing — check the project's own site. Mac Use MCP 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 computer-use and mac-use-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Computer Use has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 384 GitHub stars. Mac Use MCP has 53/100 (Good) with 0 views, 0 installs and 7 GitHub stars.