Ext Ops Panel
Open dashboard
Comparison

Gyazo vs ai.gency/gency-mcp

Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). ai.gency/gency-mcp is an MCP server published by gency.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceGyazoai.gency/gency-mcp
Docker MCP Catalog Listed
Version: sha256:0e12dbdc7b62
Forks (GitHub): 12
Pulls (Docker Hub): 16 805
Stars (Docker Hub): 0
Stars (GitHub): 28
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.0
Downloads/month (npm): 266
Downloads/week (npm): 58
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 ai.gency/gency-mcp
FactGyazoai.gency/gency-mcp
Marketplaces that list it11
Stars (GitHub) (differs)28No figure on GitHub
Pulls (Docker Hub) (differs)16 805No figure on Docker Hub
Forks (GitHub) (differs)12No figure on GitHub
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (mcp/gyazo)On your machine (@gency-ai/gency-mcp)
Transportstdiostdio
Tools it declares (differs)4Not published
Environment variables it asks for (differs)1, secrets among them: 18, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/nota/gyazo-mcp-servergithub.com/studiolab-dev/gency-mcp
Changes in the last 7 days (differs)01
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.

ai.gency/gency-mcp

In its own words, on Official MCP Registry:

Gency AI product image generation - MCP server for Claude, Codex, Cursor, VS Code

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)

ai.gency/gency-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "GENCY_MCP_UPLOAD_SECRET=<YOUR_GENCY_MCP_UPLOAD_SECRET>" --env "GENCY_OAUTH_CLIENT_SECRET=<YOUR_GENCY_OAUTH_CLIENT_SECRET>" --transport stdio gency-mcp -- npx -y @gency-ai/gency-mcp

Requires: GENCY_MCP_UPLOAD_SECRET (secret), GENCY_OAUTH_CLIENT_SECRET (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of ai.gency/gency-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 ai.gency/gency-mcp asks for

  • GENCY_API_URL
  • GENCY_MCP_ALLOWED_CLIENT_IDS
  • GENCY_MCP_OAUTH_RESOURCE
  • GENCY_MCP_UPLOAD_SECRET (secret)
  • GENCY_OAUTH_API_BASE
  • GENCY_OAUTH_CLIENT_ID
  • GENCY_OAUTH_CLIENT_SECRET (secret)
  • GENCY_OAUTH_SCOPE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Gyazo · What it can do: ai.gency/gency-mcp · 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.

Where the data comes from: how the catalog is built