Ext Ops Panel
Open dashboard
Comparison

Mobile Device MCP vs Devicely

Mobile Device MCP is an MCP server published by srmorete. Marketplaces we read that list it: 1 (Official MCP Registry). Devicely is an MCP server published by sureshkumarm8. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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
MarketplaceMobile Device MCPDevicely
Official MCP Registry Listed
Version: 0.1.10
Downloads/month (npm): 396
Downloads/week (npm): 95
Forks (GitHub): 2
Stars (GitHub): 53
Not marked · First seen
Listed
Version: 2.4.7
Forks (GitHub): 0
Stars (GitHub): 1
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

Mobile Device MCP vs Devicely
FactMobile Device MCPDevicely
Marketplaces that list it11
Stars (GitHub) (differs)53 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@srmorete/mobile-device-mcp)On your machine (devicely)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/srmorete/mobile-device-mcpgithub.com/sureshkumarm8/devicely
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-07

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

Mobile Device MCP

In its own words, on Official MCP Registry:

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

Devicely

In its own words, on Official MCP Registry:

Control real iOS & Android devices from AI agents; mirror one tap across a whole fleet.

How to run each

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

Devicely As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio devicely -- npx -y devicely 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

The marketplaces of Mobile Device MCP publish no settings it asks for, so we do not compare settings.

What it can do: Mobile Device MCP · What it can do: Devicely · 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