Ext Ops Panel
Open dashboard
Comparison

agent-device vs Mobile Device MCP

agent-device is an MCP server published by callstack. Marketplaces we read that list it: 1 (Official MCP Registry). Mobile Device MCP is an MCP server published by srmorete. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceagent-deviceMobile Device MCP
Official MCP Registry Listed
Version: 0.21.27
Downloads/month (npm): 979 627
Downloads/week (npm): 291 005
Forks (GitHub): 333
Stars (GitHub): 4 996
Not marked · First seen
Listed
Version: 0.1.10
Downloads/month (npm): 430
Downloads/week (npm): 116
Forks (GitHub): 1
Stars (GitHub): 48
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

agent-device vs Mobile Device MCP
Factagent-deviceMobile Device MCP
Marketplaces that list it11
Stars (GitHub) (differs)4 996 (better)48 (worse)
Forks (GitHub) (differs)333 (better)1 (worse)
Last release (differs)2026-10-12Not published
Where it runs (differs)On your machine (agent-device)On your machine (@srmorete/mobile-device-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/callstack/agent-devicegithub.com/srmorete/mobile-device-mcp
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

agent-device

In its own words, on Official MCP Registry:

MCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps

Mobile Device MCP

In its own words, on Official MCP Registry:

Control iOS and Android devices with multi-device and seamless Native/WebView support.

How to run each

agent-device As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-device -- npx -y agent-device mcp

Mobile Device MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mobile-device-mcp -- npx -y @srmorete/mobile-device-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: agent-device · What it can do: Mobile Device MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built