mcp-devices vs openchrome-mcp
mcp-devices is an MCP server published by AlexGladkov. Marketplaces we read that list it: 1 (npm registry (MCP servers)). openchrome-mcp is an MCP server published by shaun0927. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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
| Marketplace |  mcp-devices |  openchrome-mcp |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 4.4.1 Downloads/month (npm): 3 068 Downloads/week (npm): 876 Forks (GitHub): 37 Stars (GitHub): 384 Not marked · First seen |
Listed Version: 1.15.0 Downloads/month (npm): 806 Downloads/week (npm): 308 Forks (GitHub): 41 Stars (GitHub): 238 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
| Fact | mcp-devices | openchrome-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 384 (better) | 238 (worse) |
| Forks (GitHub) (differs) | 37 (worse) | 41 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-devices) | On your machine (openchrome-mcp) |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/alexgladkov/claude-in-mobile | github.com/shaun0927/openchrome |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-12 | 2026-10-12 |
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
mcp-devices
MCP server for mobile, desktop and browser automation — Android, iOS, HarmonyOS Next, Aurora OS, Desktop, and Browser
openchrome-mcp
Open-source browser automation MCP server. Control your real Chrome from any AI agent.
How to run each
mcp-devices
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
openchrome-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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: mcp-devices · What it can do: openchrome-mcp · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.