mobile-testing vs RobotActions — AI-Driven Mobile + Web Test Automation
mobile-testing is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
mobile-testing is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. RobotActions — AI-Driven Mobile + Web Test Automation is an MCP server published by krishtoautomate. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  RobotActions — AI-Driven Mobile + Web Test Automation | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.6 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
| Fact | mobile-testingno longer listed · | RobotActions — AI-Driven Mobile + Web Test Automation |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Not stated |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/krishtoautomate/robotactions |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of mobile-testing
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Kobiton brings agentic AI to mobile quality so engineers & testers can initiate testing directly from where code is built. With our Claude Code plugin, you can initiate Appium…
-
🧪 FAOS Master Test Architect — Master Test Architect
-
Agents that test your web and mobile app like real users, on every pull request.
-
Mobile device interaction automation via MCP
-
Drive Android & iOS mobile-app automation from your AI agent on locally connected devices.
-
tailtest automatically generates and runs tests every time Claude Code edits a file. No commands, no configuration, no reminders needed. It hooks into Claude's file write event…
What each says it does
mobile-testing
Generate mobile testing setup with Detox
RobotActions — AI-Driven Mobile + Web Test Automation
Drive real Android & iOS devices and web browsers from natural language for mobile + web QA.
How to run each
mobile-testing
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
RobotActions — AI-Driven Mobile + Web Test Automation
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: mobile-testing · What it can do: RobotActions — AI-Driven Mobile + Web Test Automation · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.