Ext Ops Panel
Open dashboard
Comparison

agent-device vs Optics

agent-device is an MCP server published by callstack. Marketplaces we read that list it: 1 (Official MCP Registry). Optics is an MCP server published by optics-framework.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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-deviceOptics
Official MCP Registry Listed
Version: 0.21.31
Downloads/month (npm): 1 021 429
Downloads/week (npm): 180 183
Forks (GitHub): 344
Stars (GitHub): 5 115
Not marked · First seen
Listed
Version: 1.11.0
Forks (GitHub): 0
Stars (GitHub): 0
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 Optics
Factagent-deviceOptics
Marketplaces that list it11
Stars (GitHub) (differs)5 115 (better)0 (worse)
Forks (GitHub) (differs)344 (better)0 (worse)
Last release (differs)2026-10-22Not published
Where it runs (differs)On your machine (agent-device)On your machine (https://github.com/mozarkai/optics-agent-plugins/releases/download/mcpb-v1.11.0/optics-framework-1.11.0.mcpb)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/callstack/agent-devicegithub.com/mozarkai/optics-agent-plugins
Changes in the last 7 days22
First seen (differs)2026-10-112026-10-20

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

Optics

In its own words, on Official MCP Registry:

Drive Android, iOS, smart TV and web apps from an agent; save the steps as CSV/YAML test suites.

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

Optics

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: agent-device · What it can do: Optics · 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