Gyazo vs HTML/CSS to Image API
Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). HTML/CSS to Image API is an MCP server published by htmlcsstoimage. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  HTML/CSS to Image API |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:0e12dbdc7b62 Forks (GitHub): 12 Pulls (Docker Hub): 16 613 Stars (Docker Hub): 0 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 7 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 | HTML/CSS to Image API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 28 (better) | 7 (worse) |
| Pulls (Docker Hub) (differs) | 16 613 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/gyazo) | Remote server (mcp.hcti.io) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/nota/gyazo-mcp-server | github.com/htmlcsstoimage/agent-plugins |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 11 h ago |
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.
HTML/CSS to Image API
Generate images and PDFs from HTML/CSS, live websites, and reusable templates.
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)
HTML/CSS to Image API As a remote MCP server
claude mcp add --transport http html-css-to-image https://mcp.hcti.ioCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only HTML/CSS to Image API has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of HTML/CSS to Image API publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of HTML/CSS to Image API publish no settings it asks for, so we do not compare settings.
What it can do: Gyazo · What it can do: HTML/CSS to Image API · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.