Ext Ops Panel
Open dashboard
Comparison

upgrade-agent vs SmartBear MCP

upgrade-agent is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-29. 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
Marketplaceupgrade-agentSmartBear MCP
Copilot CLI: github/awesome-copilot Listed
Version: 1.1.757
Forks (GitHub): 12
Stars (GitHub): 44
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.42.0
Downloads/month (npm): 34 553
Downloads/week (npm): 6 200
Forks (GitHub): 51
Stars (GitHub): 44
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:8a64acae01b6
Forks (GitHub): 51
Pulls (Docker Hub): 14 745
Stars (Docker Hub): 0
Stars (GitHub): 44
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

upgrade-agent vs SmartBear MCP
Factupgrade-agentSmartBear MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)4444
Pulls (Docker Hub) (differs)No figure on Docker Hub14 745
Forks (GitHub) (differs)12 (worse)51 (better)
Last release (differs)2026-10-28Not published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published160
Environment variables it asks for (differs)Not published17, secrets among them: 10
LicenceMITMIT
Repository (differs)github.com/microsoft/upgrade-agent-pluginsgithub.com/smartbear/smartbear-mcp
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 400 (5 days ago)

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

upgrade-agent

In its own words, on Copilot CLI: github/awesome-copilot:

AI-powered upgrade assistant for upgrading and migrating applications. Helps modernize legacy code and upgrade .NET applications to current frameworks.

SmartBear MCP

In its own words, on Official MCP Registry:

MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.

How to run each

upgrade-agent

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

SmartBear MCP As a remote MCP server

Claude Code
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)

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

Only SmartBear MCP has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of upgrade-agent publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of upgrade-agent publish no settings it asks for, so we do not compare settings.

What it can do: upgrade-agent · What it can do: SmartBear MCP · Compare two other plugins

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

Where the data comes from: how the catalog is built