Gyazo vs OpenScreenShot
Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). OpenScreenShot is an MCP server published by PGHQdev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-26. 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
| Marketplace |  Gyazo |  OpenScreenShot |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:0e12dbdc7b62 Forks (GitHub): 12 Pulls (Docker Hub): 16 963 Stars (Docker Hub): 0 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.5.2 Downloads/month (npm): 1 405 Downloads/week (npm): 480 Forks (GitHub): 7 Stars (GitHub): 90 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.5.2 Downloads/month (npm): 1 405 Downloads/week (npm): 480 Forks (GitHub): 7 Stars (GitHub): 90 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
| Fact | Gyazo | OpenScreenShot |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 28 (worse) | 90 (better) |
| Pulls (Docker Hub) (differs) | 16 963 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 7 (worse) |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | On your machine (mcp/gyazo) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/nota/gyazo-mcp-server | github.com/pghqdev/openscreenshot |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Official Model Context Protocol server for Gyazo.
OpenScreenShot
Capture website screenshots (viewport or full page) with local Chrome, or on OpenScreenShot Cloud.
How to run each
Gyazo As a local MCP server: Docker image
claude mcp add --env "GYAZO_ACCESS_TOKEN=<YOUR_GYAZO_ACCESS_TOKEN>" --transport stdio gyazo -- docker run -i --rm -e GYAZO_ACCESS_TOKEN mcp/gyazoRequires: GYAZO_ACCESS_TOKEN (secret)
OpenScreenShot As a remote MCP server
claude mcp add --transport http openscreenshot https://cloud.openscreenshot.app/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: OPENSCREENSHOT_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of OpenScreenShot publish no list of tools, so we do not compare tools.
Settings each asks for
Only Gyazo asks for
GYAZO_ACCESS_TOKEN (secret)
Only OpenScreenShot asks for
CHROME_PATHOPENSCREENSHOT_API_KEY (secret)OPENSCREENSHOT_CLOUD_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Gyazo · What it can do: OpenScreenShot · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.