Ext Ops Panel
Open dashboard
Comparison

Python Refactoring Assistant vs qa-orchestra

Python Refactoring Assistant is an MCP server published by slamer59. Marketplaces we read that list it: 1 (Docker MCP Catalog). qa-orchestra is a plugin bundle for AI coding tools published by Anasss. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
MarketplacePython Refactoring Assistantqa-orchestra
Docker MCP Catalog Listed
Version: sha256:4cd4303da424
Forks (GitHub): 6
Pulls (Docker Hub): 36 861
Stars (Docker Hub): 2
Stars (GitHub): 13
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.1.0
Forks (GitHub): 3
Stars (GitHub): 13
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

Python Refactoring Assistant vs qa-orchestra
FactPython Refactoring Assistantqa-orchestra
Marketplaces that list it11
Stars (GitHub)1313
Pulls (Docker Hub) (differs)36 861No figure on Docker Hub
Forks (GitHub) (differs)6 (better)3 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mcp-python-refactoring)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)9Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle10
LicenceMITMIT
Repository (differs)github.com/slamer59/mcp-python-refactoringgithub.com/anasss/qa-orchestra
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

Python Refactoring Assistant

In its own words, on Docker MCP Catalog:

Educational Python refactoring assistant that provides guided suggestions for AI assistants.

qa-orchestra

In its own words, on Claude Code: claude-plugins-community:

10 specialized QA agents for Claude Code. Each agent answers a specific question about your PR: Does this diff implement the acceptance criteria? What test scenarios do I need? Which existing tests will break? and writes a structured Markdown report to qa-output/ that you can paste into GitHub, Jira, or Linear. Stack-agnostic: works with any web application (React, Angular, Vue, Rails, Django, Spring Boot, etc.). Agents include: functional-reviewer (diff vs AC analysis), test-scenario-designer, smart-test-selector, bug-reporter, browser-validator (live validation via Chrome MCP), environment-manager, automation-writer (Playwright/Cypress/Selenium), release-analyzer (multi-repo diffs), manual-validator, and an orchestrator that chains them together.

How to run each

Python Refactoring Assistant As a local MCP server: Docker image

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

qa-orchestra As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install qa-orchestra@claude-community

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

Tools each declares

The marketplaces of qa-orchestra publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Python Refactoring Assistant · What it can do: qa-orchestra · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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