Ext Ops Panel
Open dashboard
Comparison

avi-migration vs SmartBear MCP

avi-migration is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

avi-migration is a plugin bundle for AI coding tools published by Randall Sclapper. No marketplace we read lists it any more. 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-28. 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

Where each is published
Marketplaceavi-migrationSmartBear MCP
Community marketplace avifoodsystems/avi-skills Removed on 2026-10-15
Version: 0.1.5
Forks (GitHub): 0
Stars (GitHub): 0
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 724
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

avi-migration vs SmartBear MCP
Factavi-migrationno longer listed · SmartBear MCP
Marketplaces that list it (differs)02
Stars (GitHub) (differs)044
Pulls (Docker Hub) (differs)No figure on Docker Hub14 724
Forks (GitHub) (differs)051
Last releaseNot publishedNot 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
Parts of the bundle (differs)2Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/avifoodsystems/avi-skillsgithub.com/smartbear/smartbear-mcp
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 400 (4 days ago)

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 avi-migration

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • upgrade-agent

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

    by microsoft · Plugin bundle

    Listed on: Copilot CLI: github/awesome-copilot · Describes nearly the same job

  • modernization-workflow

    Visualize and guide the GitHub Copilot Modernize CLI Assess, Plan, and Execute workflow for .NET, Java, and C++ application repositories.

    by EMEA App GBB · Plugin bundle

    Listed on: Copilot CLI: github/awesome-copilot · Describes nearly the same job

  • ado-aw

    Create, update, validate, operate, and debug Azure DevOps agentic workflows with ado-aw

    by GitHub Next · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • PAPI: Persistent Adaptive Project Intelligence

    Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.

    by getpapi · MCP server

    Listed on: Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces · Describes nearly the same job

  • agentic-workflow

    Doc-driven workflow skills, internal review pack, merge gates, and roadmap autopilot.

    by Gabriel Trabanco · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • work-unit-roadmap

    An AI agent workflow for professional software development using roadmap-driven execution, atomic Work Units, verification evidence, and one verified commit per completed unit. It…

    by truong170201 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

avi-migration

In its own words, on Community GitHub marketplaces:

Plan AVI .NET 10 API migrations and create developer-ready GitHub Project iteration stories

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

avi-migration

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 avi-migration publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: avi-migration · What it can do: SmartBear MCP · 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. 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