Ext Ops Panel
Open dashboard
Comparison

visual-pr vs Chrome DevTools MCP

visual-pr is a plugin bundle for AI coding tools published by Awesome Copilot Community. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Chrome DevTools MCP is an MCP server published by ChromeDevTools. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot, Community GitHub marketplaces, 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
Marketplacevisual-prChrome DevTools MCP
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.0
Forks (GitHub): 5 103
Stars (GitHub): 39 955
Not marked · First seen
Listed
Version: 1.0.1
Forks (GitHub): 6 332
Stars (GitHub): 53 344
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.10.1
Downloads/month (npm): 7 493 150
Downloads/week (npm): 1 060 392
Forks (GitHub): 6 332
Stars (GitHub): 53 344
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 1.9.0
Forks (GitHub): 6 332
Stars (GitHub): 53 344
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.6.0
Forks (GitHub): 6 332
Stars (GitHub): 53 344
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

visual-pr vs Chrome DevTools MCP
Factvisual-prChrome DevTools MCP
Marketplaces that list it (differs)1 (worse)5 (better)
Stars (GitHub) (differs)39 955 (worse)53 344 (better)
Forks (GitHub) (differs)5 103 (worse)6 332 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (chrome-devtools-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published8
Licence (differs)MITApache-2.0
Repository (differs)github.com/github/awesome-copilotgithub.com/chromedevtools/chrome-devtools-mcp
Changes in the last 7 days (differs)07
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

visual-pr

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

Capture, annotate, and embed screenshots and animated GIF demos in pull request descriptions. Includes Playwright-based UI capture, PIL image annotations, PR embedding workflows for GitHub and Azure DevOps, and screen recording with variable timing.

Chrome DevTools MCP

In its own words, on Official MCP Registry:

MCP server for Chrome DevTools

How to run each

visual-pr

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

Chrome DevTools MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio chrome-devtools-mcp -- npx -y chrome-devtools-mcp

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: visual-pr · What it can do: Chrome DevTools MCP · 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 the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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