Goodeye vs gflow-cli
Goodeye is an MCP server published by goodeye.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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-16. 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 |  Goodeye |  gflow-cli |
|---|---|---|
| Official MCP Registry | Listed Version: 0.19.2 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.85.0 Downloads/month (PyPI): 6 947 Downloads/week (PyPI): 1 840 Forks (GitHub): 85 Stars (GitHub): 295 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 | Goodeye | gflow-cli |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (worse) | 295 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 85 (better) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Remote server (mcp.goodeye.dev/mcp) | On your machine (gflow-cli) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/goodeye-labs/goodeye-cli | github.com/ffroliva/gflow-cli |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no remote endpoint we check |
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
Goodeye
Design, save, and run outcome-aligned AI workflows and verifiers, with reliable image output.
gflow-cli
Drive Google Flow from an agent: Veo video and Imagen image generation
How to run each
Goodeye As a remote MCP server
claude mcp add --transport http goodeye https://mcp.goodeye.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
gflow-cli As a local MCP server: PyPI package
claude mcp add --transport stdio gflow-cli -- uvx gflow-cli mcp runCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Goodeye has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Goodeye publish no settings it asks for, so we do not compare settings.
What it can do: Goodeye · What it can do: gflow-cli · Compare two other plugins
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.