Ext Ops Panel
Open dashboard
Comparison

testing vs io.github.mobile-next/mobile-mcp

testing is a plugin bundle for AI coding tools published by kobiton. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.mobile-next/mobile-mcp is an MCP server published by mobile-next. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
Marketplacetestingio.github.mobile-next/mobile-mcp
Claude Code: claude-plugins-community Listed
Version: 1.9.0
Forks (GitHub): 5
Stars (GitHub): 13
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.11
Downloads/month (npm): 229 945
Downloads/week (npm): 51 112
Forks (GitHub): 852
Stars (GitHub): 9 568
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

testing vs io.github.mobile-next/mobile-mcp
Facttestingio.github.mobile-next/mobile-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)13 (worse)9 568 (better)
Forks (GitHub) (differs)5 (worse)852 (better)
Last release (differs)Not published2026-10-14
Where it runs (differs)Remote server (api.kobiton.com/mcp)On your machine (@mobilenext/mobile-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)91
Licence (differs)MITApache-2.0
Repository (differs)github.com/kobiton/automategithub.com/mobile-next/mobile-mcp
Changes in the last 7 days (differs)04
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 2 days agono remote endpoint we check

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

testing

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

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 tests and inspect results on real devices without leaving your development workflow. You can manage test execution, save apps for future testing, review test execution results, work with a range of different real devices.

io.github.mobile-next/mobile-mcp

In its own words, on Official MCP Registry:

MCP server for iOS and Android Mobile Development, Automation and Testing

How to run each

testing As a Claude Code plugin

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

io.github.mobile-next/mobile-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mobile-mcp -- npx -y @mobilenext/mobile-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only testing has a remote endpoint we check. How we check endpoints

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: testing · What it can do: io.github.mobile-next/mobile-mcp · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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