SmartBear MCP vs agent-device
SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). 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-15. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.42.0 Downloads/month (npm): 47 525 Downloads/week (npm): 10 500 Forks (GitHub): 50 Stars (GitHub): 44 Not marked · First seen |
Listed Version: 0.21.27 Downloads/month (npm): 979 627 Downloads/week (npm): 291 005 Forks (GitHub): 334 Stars (GitHub): 5 010 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:8a64acae01b6 Forks (GitHub): 50 Pulls (Docker Hub): 14 339 Stars (Docker Hub): 0 Stars (GitHub): 44 Not marked · First seen |
Not listed |
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 | SmartBear MCP | agent-device |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 44 (worse) | 5 010 (better) |
| Pulls (Docker Hub) (differs) | 14 339 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 50 (worse) | 334 (better) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Remote server or your machine | On your machine (agent-device) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 160 | Not published |
| Environment variables it asks for (differs) | 17, secrets among them: 10 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/smartbear/smartbear-mcp | github.com/callstack/agent-device |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no 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
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
agent-device
MCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps
How to run each
SmartBear MCP As a remote MCP server
claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcp
Requires: BEARQ_API_TOKEN (secret), BUGSNAG_AUTH_TOKEN (secret), PACT_BROKER_PASSWORD (secret), PACT_BROKER_TOKEN (secret), QTM4J_API_KEY (secret), QTM4J_AUTOMATION_API_KEY (secret), REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), ZEPHYR_API_TOKEN (secret)
agent-device As a local MCP server: npm package
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
The marketplaces of agent-device publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of agent-device publish no settings it asks for, so we do not compare settings.
What it can do: SmartBear MCP · What it can do: agent-device · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.