Comparison

Gyazo vs Glif

Gyazo is an MCP server published by nota. Marketplaces we read that list it: 1 (Docker MCP Catalog). Glif is an MCP server published by glif.app. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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
Marketplace	Gyazo	Glif
Docker MCP Catalog	Listed Version: sha256:0e12dbdc7b62 Forks (GitHub): 12 Pulls (Docker Hub): 16 667 Stars (Docker Hub): 0 Stars (GitHub): 28 Not marked · First seen 2026-10-11	Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 33 Pulls (Docker Hub): 19 708 Stars (Docker Hub): 2 Stars (GitHub): 215 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 1.0.1 Forks (GitHub): 33 Stars (GitHub): 215 Not marked · First seen 2026-10-11

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 Glif
Fact	Gyazo	Glif
Marketplaces that list it (differs)	1 (worse)	3 (better)
Stars (GitHub) (differs)	28 (worse)	215 (better)
Pulls (Docker Hub) (differs)	16 667 (worse)	19 708 (better)
Forks (GitHub) (differs)	12 (worse)	33 (better)
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/gyazo)	Remote server or your machine
Transport (differs)	stdio	Streamable HTTP, stdio
Tools it declares (differs)	4	10
Environment variables it asks for (differs)	1, secrets among them: 1	3, secrets among them: 1
Parts of the bundle (differs)	Not a bundle	11
Licence	MIT	MIT
Repository (differs)	github.com/nota/gyazo-mcp-server	github.com/glifxyz/glif-mcp-server
Changes in the last 7 days (differs)	0	2
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Responded 41 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

In its own words, on Docker MCP Catalog:

Official Model Context Protocol server for Gyazo.

Glif

In its own words, on Official MCP Registry:

Generate images, video, and audio with Glif's media-generation agent

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)

Glif As a remote MCP server

Claude Code

claude mcp add --transport http glif https://glif.app/api/mcp

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

Only Glif has a remote endpoint we check. How we check endpoints

Tools each declares

Only Gyazo declares

gyazo_image
gyazo_latest_image
gyazo_search
gyazo_upload

Only Glif declares

glif_info
list_featured_glifs
list_saved_glif_tools
my_glif_user_info
my_glifs
remove_all_glif_tools
remove_glif_tool
run_glif
save_glif_as_tool
search_glifs

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Gyazo asks for

GYAZO_ACCESS_TOKEN (secret)

Only Glif asks for

GLIF_API_TOKEN (secret)
GLIF_IDS
IGNORE_SAVED_GLIFS

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

What it can do: Gyazo · What it can do: Glif · 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. 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 2026-10-18. We publish no contact details for plugin publishers.