Ext Ops Panel
Open dashboard
Comparison

prodmaster-ai vs Feedbacks

prodmaster-ai is a plugin bundle for AI coding tools published by sujithkrishnan-dev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Feedbacks is an MCP server published by Softinator-TechLabs. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceprodmaster-aiFeedbacks
Claude Code: claude-plugins-community Listed
Version: 2.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.2
Forks (GitHub): 0
Stars (GitHub): 34
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

prodmaster-ai vs Feedbacks
Factprodmaster-aiFeedbacks
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)34 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/Softinator-TechLabs/feedbacks-plugins/releases/download/v0.2.2/feedbacks-mcp-0.2.2.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)4Not published
Parts of the bundle (differs)36Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/sujithkrishnan-dev/prodmaster-aigithub.com/softinator-techlabs/feedbacks-oss
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

prodmaster-ai

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

Full-stack engineering ops for Claude Code. One command (/prodmasterai) covers your entire dev lifecycle: orchestrate features into parallel tasks, run 11-phase QA with health scoring, enforce two-pass code review, deploy with dry-run and revert, audit security across 14 OWASP+STRIDE phases, scan dependencies for CVEs, benchmark Core Web Vitals, and run cross-model adversarial review. 31 skills, 4 active safety hooks. The plugin self-improves using velocity data from your completed cycles — no manual tuning needed.

Feedbacks

In its own words, on Official MCP Registry:

Visual website feedback, screenshots and team discussion for coding assistants. Self-hosted.

How to run each

prodmaster-ai As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install prodmaster-ai@claude-community

Feedbacks

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

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

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

What it can do: prodmaster-ai · What it can do: Feedbacks · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-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