Ext Ops Panel
Open dashboard
Comparison

agentiqa vs agent-device

agentiqa is a plugin bundle for AI coding tools published by Agentiqa. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). agent-device is an MCP server published by callstack. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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

Where each is published
Marketplaceagentiqaagent-device
Claude Code: claude-plugins-community Listed
Version: 0.5.3
Forks (GitHub): 2
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.21.27
Downloads/month (npm): 979 627
Downloads/week (npm): 291 005
Forks (GitHub): 333
Stars (GitHub): 4 986
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

agentiqa vs agent-device
Factagentiqaagent-device
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)4 986 (better)
Forks (GitHub) (differs)2 (worse)333 (better)
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleOn your machine (agent-device)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agentiqa/agentiqa-plugingithub.com/callstack/agent-device
Changes in the last 7 days (differs)02
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

agentiqa

In its own words, on Claude Code: claude-plugins-community:

AI-powered QA testing agent for web and mobile apps. Agentiqa explores your app visually - like a real user with fresh eyes - and reports bugs with severity, confidence scores, and step-by-step reproduction instructions. No selectors, no scripts, no test code to maintain. Just describe what to test in plain English. Supports web (any URL or localhost), Android (emulator/device), and iOS (simulator/device). Finds visual bugs, logical errors, UX issues, and accessibility problems that unit tests and linters miss.

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

How to run each

agentiqa As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agentiqa@claude-community

agent-device As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-device -- npx -y agent-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: agentiqa · What it can do: agent-device · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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