Gyazo vs pixelforge-mcp
pixelforge-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). pixelforge-mcp is a plugin bundle for AI coding tools published by freema. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:0e12dbdc7b62 Forks (GitHub): 12 Pulls (Docker Hub): 16 703 Stars (Docker Hub): 0 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Community marketplace freema/pixelforge-mcp | Not listed | Removed on 2026-10-20 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 5 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 | pixelforge-mcpno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 28 | 5 |
| Pulls (Docker Hub) (differs) | 16 703 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/gyazo) | On your machine (pixelforge-mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/nota/gyazo-mcp-server | github.com/freema/pixelforge-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-19 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of pixelforge-mcp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Generate, edit, style-match, turn, and animate game-ready pixel art at exact sizes.
-
Generate pixel art sprites, animations, 8-direction rotations and palettes for games.
-
Pixel art and sprite animation for agents: JSON recipes to PNG, APNG, GIF and sprite sheets.
-
Generate authentic pixel art - sprites, animations, and tilesets - from any MCP client
-
Generate game art from Claude. Adds the SpriteCook MCP server for creating pixel art sprites, textures, and animations, plus guided skills for sprite sheets, tilesets, and icon…
-
Generate and manage 2D game sprites using Google Gemini's image generation. This plugin acts as a creative director — it asks about your art style, view angle, and game context…
What each says it does
Gyazo
Official Model Context Protocol server for Gyazo.
pixelforge-mcp
Forge pixel art sprites, animations, backgrounds & thumbnails using Google Gemini
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/gyazo
Requires: GYAZO_ACCESS_TOKEN (secret)
pixelforge-mcp
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 pixelforge-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
Only Gyazo asks for
GYAZO_ACCESS_TOKEN (secret)
Only pixelforge-mcp asks for
GEMINI_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Gyazo · What it can do: pixelforge-mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.