Desktop MCP vs Agent Device
A side-by-side look at the Desktop MCP and Agent Device MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Desktop MCP 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?
Choose Desktop MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Choose Agent Device when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 37/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,133 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Desktop MCP | View Agent Device |
Tools & capabilities
Desktop MCP tools
No tool names declared yet. Check the project README from 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.
Desktop MCP
{
"mcpServers": {
"desktop-mcp": {
"command": "uvx",
"args": [
"desktop-mcp"
]
}
}
}
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.