Ext Ops Panel
Open dashboard
Comparison

JetBrains vs io.github.Weavatrix/weavatrix-refactor

JetBrains is an MCP server published by GannaChernyshova. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-16. 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
MarketplaceJetBrainsio.github.Weavatrix/weavatrix-refactor
Docker MCP Catalog Listed
Version: sha256:a662cac15c5d
Forks (GitHub): 7
Pulls (Docker Hub): 59 195
Stars (Docker Hub): 2
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.11
Downloads/month (npm): 482
Downloads/week (npm): 88
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

JetBrains vs io.github.Weavatrix/weavatrix-refactor
FactJetBrainsio.github.Weavatrix/weavatrix-refactor
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)1 (worse)
Pulls (Docker Hub) (differs)59 195No figure on Docker Hub
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/jetbrains)On your machine (weavatrix-refactor)
Transportstdiostdio
Tools it declares (differs)30Not published
Environment variables it asks for1, secrets among them: 01, secrets among them: 0
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/gannachernyshova/mcp-jetbrainsgithub.com/weavatrix/weavatrix-refactor
Changes in the last 7 days (differs)04
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

JetBrains

In its own words, on Docker MCP Catalog:

A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio.

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

JetBrains As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio jetbrains -- docker run -i --rm mcp/jetbrains

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 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 io.github.Weavatrix/weavatrix-refactor publish no list of tools, so we do not compare tools.

Settings each asks for

Only JetBrains asks for

  • IDE_PORT

Only io.github.Weavatrix/weavatrix-refactor asks for

  • WEAVATRIX_ALLOW_SOURCE_EDITS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: JetBrains · What it can do: io.github.Weavatrix/weavatrix-refactor · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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