google-flow-mcp vs Glif
google-flow-mcp is an MCP server published by joshuadaniel-8090. Marketplaces we read that list it: 1 (PyPI (MCP servers)). 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-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
| Marketplace |   Glif | |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.1.0 Downloads/month (PyPI): 171 Downloads/week (PyPI): 106 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 32 Stars (GitHub): 218 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 32 Pulls (Docker Hub): 20 188 Stars (Docker Hub): 2 Stars (GitHub): 218 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 | google-flow-mcp | Glif |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 218 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 20 188 |
| Forks (GitHub) (differs) | No figure on GitHub | 32 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (google-flow-mcp) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 10 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 11 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/joshuadaniel-8090/google-flow-mcp | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 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
google-flow-mcp
MCP server giving Claude Desktop access to Google AI image and video generation
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
google-flow-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Glif As a remote MCP server
claude mcp add --transport http glif https://glif.app/api/mcpCommands 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
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: google-flow-mcp · What it can do: Glif · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.