What is the key difference between Desktop Touch MCP and Agent Device?

Desktop Touch MCP belongs to the OS Automation category with local stdio execution, while Agent Device belongs to the OS Automation category with local stdio execution.

How do I install Desktop Touch MCP or Agent Device in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Desktop Touch MCP and Agent Device free or paid?

Desktop Touch MCP operates under a Free / Open Source model (No auth required). Agent Device operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Desktop Touch MCP lists 23 tools with 2 views and 22 GitHub stars. Agent Device lists 5 tools with 1 views and 4,696 GitHub stars.

Can I use both Desktop Touch MCP and Agent Device together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Desktop Touch MCP vs Agent Device

In-depth architectural comparison of the Desktop Touch MCP and Agent Device MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Desktop Touch MCP

OS Automation · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Agent Device

OS Automation · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

Verdict Summary: Choose Desktop Touch MCP if you need specialized OS Automation tools running via a local process. Choose Agent Device if your workspace requires OS Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Desktop Touch MCP when:

You need dedicated capabilities in the OS Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: desktop_discover, desktop_act, desktop_state.

Explore Desktop Touch MCP Details

Choose Agent Device when:

You need dedicated capabilities in the OS Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Cross-platform support for iOS, Android, tvOS, macOS, Linux, and web, Accessibility tree snapshots with token-efficient element references, UI actions including press, fill, scroll, wait, and alert handling.

Feature & Specification Comparison

Specification	Desktop Touch MCP Harusame64 OS Automation	Agent Device callstackincubator OS Automation
Summary	Windows desktop automation for LLM agents with entity-based actions instead of coordinate-only clicking. Uses UIA, CDP, screenshots, keyboard/mouse/clipboard, and terminal control, plus entity leases, verified delivery, causal context, and interaction memory to reduce silent UI automation failures.	Discovery 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.
Category & Scope

Tools & Capabilities Breakdown

Desktop Touch MCP Tools (23)

desktop_discover

Observe the desktop. Returns interactive entities with leases (UIA, CDP, Terminal, Visual SoM).

desktop_act

Perform actions (click, type, drag, select) on entities via lease validation. Returns semantic diffs — plus an optional `roiCapture` (changed-region PNG + next-target preview) on visual-only targets.

desktop_state

Lightweight check of focus, active window, cursor, and Auto-Perception attention signal.

screenshot

Multi-mode capture: `detail='text'` (UIA/OCR), `diffMode` (P-frame), `dotByDot` (1:1), and `background`. Returns a cheap `screenshot://by-ref/{id}` link to the saved image instead of inlining pixels every time.

screenshot_query

Inspect and prune the on-disk screenshot cache behind the by-ref links: `screenshot_query` lists saved captures without re-reading pixels; `screenshot_gc` reclaims space by retention policy (dry-run by default).

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Desktop Touch MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "harusame64-desktop-touch-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@harusame64/desktop-touch-mcp"
      ]
    }
  }
}

Agent Device Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "callstackincubator-agent-device": {
      "command": "npx",
      "args": [
        "-y",
        "callstackincubator-agent-device"
      ]
    }
  }
}

Frequently Asked Questions

Desktop Touch MCP is categorized under OS Automation and uses a local stdio subprocess. In contrast, Agent Device belongs to OS Automation using local stdio subprocess. Select Desktop Touch MCP when you need capabilities focused on os automation and Agent Device when you require tools for os automation.

More alternatives to Desktop Touch MCP More alternatives to Agent Device OS Automation category hub Canonical compare URL