Ext Ops Panel
Open dashboard
Comparison

EverArt (Archived) vs google-flow-mcp

EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). google-flow-mcp is an MCP server published by joshuadaniel-8090. Marketplaces we read that list it: 1 (PyPI (MCP servers)). As of our marketplace pass on 2026-11-11. 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)google-flow-mcp
Docker MCP Catalog Listed
Version: sha256:98c2aa1b6231
Forks (GitHub): 11 930
Pulls (Docker Hub): 19 280
Stars (Docker Hub): 3
Stars (GitHub): 91 903
Not marked · First seen
Not listed
PyPI (MCP servers) Not listed Listed
Version: 0.1.0
Downloads/month (PyPI): 171
Downloads/week (PyPI): 106
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 google-flow-mcp
FactEverArt (Archived)google-flow-mcp
Marketplaces that list it11
Stars (GitHub) (differs)91 903No figure on GitHub
Pulls (Docker Hub) (differs)19 280No figure on Docker Hub
Forks (GitHub) (differs)11 930No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/everart)On your machine (google-flow-mcp)
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/joshuadaniel-8090/google-flow-mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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.

google-flow-mcp

In its own words, on PyPI (MCP servers):

MCP server giving Claude Desktop access to Google AI image and video 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)

google-flow-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 google-flow-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of google-flow-mcp publish no settings it asks for, so we do not compare settings.

What it can do: EverArt (Archived) · What it can do: google-flow-mcp · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). 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