ZennoDroid: device in ProjectMaker vs io.github.vladkarpman/device-manager-mcp
ZennoDroid: device in ProjectMaker is an MCP server published by zennolab.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vladkarpman/device-manager-mcp is an MCP server published by vladkarpman. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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 |  ZennoDroid: device in ProjectMaker | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.0 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Listed Version: 1.0.7 Downloads/month (PyPI): 154 Downloads/week (PyPI): 67 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 | ZennoDroid: device in ProjectMaker | io.github.vladkarpman/device-manager-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-21 | Not published |
| Where it runs (differs) | On your machine (https://github.com/ZennoLab/zennoposter-mcp/releases/download/mcp-android-v0.6.0/MCP.Android-android-pm-v0.6.0-win-x64.mcpb) | On your machine (device-manager-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/zennolab/zennoposter-mcp | github.com/vladkarpman/device-manager-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
ZennoDroid: device in ProjectMaker
Drive the Android device attached to ZennoDroid ProjectMaker: screen, elements, apps, gestures.
io.github.vladkarpman/device-manager-mcp
MCP server for fast Android device interaction with scrcpy acceleration (~50ms latency).
How to run each
ZennoDroid: device in ProjectMaker
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.vladkarpman/device-manager-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio device-manager-mcp -- uvx device-manager-mcpCommands 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: ZennoDroid: device in ProjectMaker · What it can do: io.github.vladkarpman/device-manager-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.