DNS DATA Remote MCP vs Mobilerun

A side-by-side look at the DNS DATA Remote MCP and Mobilerun MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

DNS 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.0Mobilerun logoMobilerunOS Automation · Local subprocess (stdio)Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.49FairAuth: not declared

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

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

Mobilerun logoChoose Mobilerun when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDNS DATA Remote MCP logoDNS DATA Remote MCPMobilerun logoMobilerun
CategoryOS AutomationOS Automation
Quality signal74/100 · Great49/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthOAuth 2.0Not declared
PricingFreemiumNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars19,746
Directory activity 7 views 0 installs 1 upvotes 7 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

DNS DATA Remote MCP tools

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

Mobilerun 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.

DNS DATA Remote MCP

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

Mobilerun

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mobilerun": {
      "command": "uvx",
      "args": [
        "mobilerun"
      ]
    }
  }
}

Frequently asked questions

DNS DATA Remote MCP is categorized under OS Automation and uses a remote HTTP/SSE transport. Mobilerun belongs to OS Automation and uses a local stdio subprocess. Pick DNS DATA Remote MCP for os automation work and Mobilerun 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.

DNS DATA Remote MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Mobilerun 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 dns-data-remote-mcp and mobilerun as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, DNS DATA Remote MCP has a quality signal of 74/100 (Great) with 7 views, 0 installs and 1 GitHub stars. Mobilerun has 49/100 (Fair) with 7 views, 0 installs and 9,746 GitHub stars.