Agent Device vs Computer Use

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

Agent 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.52GoodAuth: no auth requiredComputer Use logoComputer UseOS Automation · Local subprocess (stdio)Control your computer with screenshots, mouse, and keyboard automation.49FairAuth: not declared

Verdict: choose Agent Device for os automation work; choose Computer Use 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?

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

Computer Use logoChoose Computer Use when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Computer Use

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Device logoAgent DeviceComputer Use logoComputer Use
CategoryOS AutomationOS Automation
Quality signal52/100 · Good49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5,123387
Directory activity 3 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Agent Device tools

No tool names declared yet. Check the project README from the listing page.

Computer Use 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.

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.

Computer Use

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "computer-use": {
      "command": "npx",
      "args": [
        "-y",
        "computer-use-mcp"
      ]
    }
  }
}

Frequently asked questions

Agent Device is categorized under OS Automation and uses an install path we have not confirmed yet. Computer Use belongs to OS Automation and uses a local stdio subprocess. Pick Agent Device for os automation work and Computer Use 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.

Agent Device is listed as free. Auth: no auth required. Computer Use 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 callstackincubator-agent-device and computer-use as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agent Device has a quality signal of 52/100 (Good) with 3 views, 0 installs and 5,123 GitHub stars. Computer Use has 49/100 (Fair) with 2 views, 0 installs and 387 GitHub stars.