Ext Ops Panel
Open dashboard
Comparison

modernize-java vs io.github.Weavatrix/weavatrix-refactor

modernize-java is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). io.github.Weavatrix/weavatrix-refactor is an MCP server published by Weavatrix. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
Marketplacemodernize-javaio.github.Weavatrix/weavatrix-refactor
Copilot CLI: github/awesome-copilot Listed
Version: 1.24.0
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.11
Forks (GitHub): 0
Stars (GitHub): 1
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

modernize-java vs io.github.Weavatrix/weavatrix-refactor
Factmodernize-javaio.github.Weavatrix/weavatrix-refactor
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)1 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (weavatrix-refactor)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/modernize-javagithub.com/weavatrix/weavatrix-refactor
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

modernize-java

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

GitHub Copilot modernization – Java Upgrade CLI Plugin helps you upgrade Java applications from the command line. It brings intelligent modernization capabilities to your terminal and CI/CD pipelines: analyze your project and generate an upgrade plan, automatically transform your codebase, fix build issues, validate against known CVEs, and output a detailed summary of file changes and updated dependencies.

io.github.Weavatrix/weavatrix-refactor

In its own words, on Official MCP Registry:

Transactional refactoring extension with 11 evidence-backed tools, previews, and rollback.

How to run each

modernize-java

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

io.github.Weavatrix/weavatrix-refactor As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio weavatrix-refactor -- npx -y weavatrix-refactor

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: modernize-java · What it can do: io.github.Weavatrix/weavatrix-refactor · 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. 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