Ext Ops Panel
Open dashboard
Comparison

Gyazo vs peepshow

Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). peepshow is a plugin bundle for AI coding tools published by t0mtaylor. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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
MarketplaceGyazopeepshow
Docker MCP Catalog Listed
Version: sha256:0e12dbdc7b62
Forks (GitHub): 12
Pulls (Docker Hub): 16 594
Stars (Docker Hub): 0
Stars (GitHub): 28
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.9.0
Forks (GitHub): 13
Stars (GitHub): 68
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

Gyazo vs peepshow
FactGyazopeepshow
Marketplaces that list it11
Stars (GitHub) (differs)28 (worse)68 (better)
Pulls (Docker Hub) (differs)16 594No figure on Docker Hub
Forks (GitHub) (differs)12 (worse)13 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/gyazo)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)4Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle4
Licence (differs)MITNot stated
Repository (differs)github.com/nota/gyazo-mcp-servergithub.com/t0mtaylor/peepshow
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

Gyazo

In its own words, on Docker MCP Catalog:

Official Model Context Protocol server for Gyazo.

peepshow

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

Turn videos + animated images into a timeline of still frames so LLMs can watch them. CLI + Claude Code plugin with 19 pluggable sinks.

How to run each

Gyazo As a local MCP server: Docker image

Claude Code
claude mcp add --env "GYAZO_ACCESS_TOKEN=<YOUR_GYAZO_ACCESS_TOKEN>" --transport stdio gyazo -- docker run -i --rm -e GYAZO_ACCESS_TOKEN mcp/gyazo

Requires: GYAZO_ACCESS_TOKEN (secret)

peepshow

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

The marketplaces of peepshow publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of peepshow publish no settings it asks for, so we do not compare settings.

What it can do: Gyazo · What it can do: peepshow · 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