Ext Ops Panel
Open dashboard
Comparison

upgrade-agent vs ExactGround

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). ExactGround is an MCP server published by alidaram99. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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-agentExactGround
Copilot CLI: github/awesome-copilot Listed
Version: 1.1.652
Forks (GitHub): 9
Stars (GitHub): 41
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
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

upgrade-agent vs ExactGround
Factupgrade-agentExactGround
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)41 (better)0 (worse)
Forks (GitHub) (differs)9 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (dropin-apis--exactground-api.apify.actor/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not published2
LicenceMITMIT
Repository (differs)github.com/microsoft/upgrade-agent-pluginsgithub.com/alidaram99/exactground
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 14 h ago, requires a key

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.

ExactGround

In its own words, on Official MCP Registry:

Check npm/PyPI packages exist and that a function or method exists in an exact package version.

How to run each

upgrade-agent

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

ExactGround As a remote MCP server

Claude Code
claude mcp add --transport http exactground https://dropin-apis--exactground-api.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only ExactGround 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: upgrade-agent · What it can do: ExactGround · 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 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