Ext Ops Panel
Open dashboard
Comparison

ui-screenshot vs OpenScreenShot

ui-screenshot is a plugin bundle for AI coding tools published by gabrielkoerich. Marketplaces we read that list it: 1 (Community GitHub marketplaces). OpenScreenShot is an MCP server published by PGHQdev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
Marketplaceui-screenshotOpenScreenShot
Community marketplace gabrielkoerich/skills Not seen in the last pass
Version: not stated
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.5.1
Downloads/month (npm): 1 546
Downloads/week (npm): 215
Forks (GitHub): 7
Stars (GitHub): 86
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

ui-screenshot vs OpenScreenShot
Factui-screenshotOpenScreenShot
Marketplaces that list it11
Stars (GitHub) (differs)6 (worse)86 (better)
Forks (GitHub) (differs)0 (worse)7 (better)
Last release (differs)Not published2026-10-17
Where it runs (differs)Installs as a plugin bundleOn your machine (openscreenshot)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/gabrielkoerich/skillsgithub.com/pghqdev/openscreenshot
Changes in the last 7 days (differs)23
First seen (differs)2026-10-192026-10-13

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

ui-screenshot

In its own words, on Community GitHub marketplaces:

Capture a PNG screenshot of any URL with a headless Chromium-family browser over CDP (Brave preferred, no Playwright needed), with phone viewports, browser language lists and a layout check. Use it whenever the user asks you to look at, check or visually verify a page or a frontend change, test it on mobile, or test a language redirect. Output PNG goes to /tmp/ui-shot.png by default; read it back with the Read tool.

OpenScreenShot

In its own words, on Official MCP Registry:

Capture website screenshots (viewport or full page) with your installed Chrome. Runs locally.

How to run each

ui-screenshot As a Claude Code plugin

Claude Code
/plugin marketplace add gabrielkoerich/skills
/plugin install ui-screenshot@skills

OpenScreenShot As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio openscreenshot -- npx -y openscreenshot

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 ui-screenshot publish no settings it asks for, so we do not compare settings.

What it can do: ui-screenshot · What it can do: OpenScreenShot · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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