Agent Device vs DNS DATA Remote MCP

A side-by-side look at the Agent Device and DNS DATA Remote MCP 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 AutomationMCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps45FairAuth: no auth requiredDNS DATA Remote MCP logoDNS DATA Remote MCPOS Automation · Remote HTTP/SSEHosted remote MCP via Streamable HTTP and OAuth at https://mcp.dns-data.com/mcp. Connect compatible AI clients to authorized Windows/macOS computers for approved file, system and command operations.74GreatAuth: oauth 2.0

Verdict: choose Agent Device for os automation work; choose DNS DATA Remote MCP for os automation over a hosted endpoint. 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

DNS DATA Remote MCP logoChoose DNS DATA Remote MCP when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore DNS DATA Remote MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Device logoAgent DeviceDNS DATA Remote MCP logoDNS DATA Remote MCP
CategoryOS AutomationOS Automation
Quality signal45/100 · Fair74/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNo auth requiredOAuth 2.0
PricingFreeFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars5,1251
Directory activity 4 views 0 installs 0 upvotes 7 views 0 installs 1 upvotes
ToolsNot listedNot listed

Tools & capabilities

Agent Device tools

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

DNS DATA Remote MCP 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.

DNS DATA Remote MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dns-data-remote-mcp": {
      "url": "https://mcp.dns-data.com/mcp"
    }
  }
}

Frequently asked questions

Agent Device is categorized under OS Automation and uses an install path we have not confirmed yet. DNS DATA Remote MCP belongs to OS Automation and uses a remote HTTP/SSE transport. Pick Agent Device for os automation work and DNS DATA Remote 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. Agent Device has no confirmed install command yet — follow its own setup instructions.

Agent Device is listed as free. Auth: no auth required. DNS DATA Remote MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 agent-device and dns-data-remote-mcp 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 45/100 (Fair) with 4 views, 0 installs and 5,125 GitHub stars. DNS DATA Remote MCP has 74/100 (Great) with 7 views, 0 installs and 1 GitHub stars.