Ext Ops Panel
Open dashboard
Comparison

EverArt (Archived) vs gflow-cli

EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). gflow-cli is an MCP server published by ffroliva. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceEverArt (Archived)gflow-cli
Docker MCP Catalog Listed
Version: sha256:98c2aa1b6231
Forks (GitHub): 11 780
Pulls (Docker Hub): 18 780
Stars (Docker Hub): 3
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.84.0
Downloads/month (PyPI): 6 947
Downloads/week (PyPI): 1 840
Forks (GitHub): 79
Stars (GitHub): 279
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

EverArt (Archived) vs gflow-cli
FactEverArt (Archived)gflow-cli
Marketplaces that list it11
Stars (GitHub) (differs)91 180 (better)279 (worse)
Pulls (Docker Hub) (differs)18 780No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)79 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/everart)On your machine (gflow-cli)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/ffroliva/gflow-cli
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

EverArt (Archived)

In its own words, on Docker MCP Catalog:

Image generation server using EverArt's API.

gflow-cli

In its own words, on Official MCP Registry:

Drive Google Flow from an agent: Veo video and Imagen image generation

How to run each

EverArt (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "EVERART_API_KEY=<YOUR_EVERART_API_KEY>" --transport stdio everart -- docker run -i --rm -e EVERART_API_KEY mcp/everart

Requires: EVERART_API_KEY (secret)

gflow-cli As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio gflow-cli -- uvx gflow-cli mcp run

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

Tools each declares

The marketplaces of gflow-cli publish no list of tools, so we do not compare tools.

Settings each asks for

Only EverArt (Archived) asks for

  • EVERART_API_KEY (secret)

Only gflow-cli asks for

  • GFLOW_CLI_HOME

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

What it can do: EverArt (Archived) · What it can do: gflow-cli · 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