MetaDock vs Agent Device
A side-by-side look at the MetaDock 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 MetaDock for os automation work over a hosted endpoint; choose Agent Device for os automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose MetaDock when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE 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 | M MetaDock | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 38/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| 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 | — | 5,115 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MetaDock | View Agent Device |
Tools & capabilities
MetaDock 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.
MetaDock
{
"mcpServers": {
"metadock": {
"url": "https://metadock.app/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.