Ext Ops Panel
Open dashboard
Comparison

flux-3-video vs Glif

flux-3-video is a plugin bundle for AI coding tools published by Black Forest Labs. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-28. 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
Marketplaceflux-3-videoGlif
Community marketplace black-forest-labs/skills Listed
Version: not stated
Forks (GitHub): 11
Stars (GitHub): 135
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 32
Stars (GitHub): 216
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:3f93ddceeb99
Forks (GitHub): 32
Pulls (Docker Hub): 20 025
Stars (Docker Hub): 2
Stars (GitHub): 216
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

flux-3-video vs Glif
Factflux-3-videoGlif
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)135 (worse)216 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub20 025
Forks (GitHub) (differs)11 (worse)32 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published10
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)811
Licence (differs)Not statedMIT
Repository (differs)github.com/black-forest-labs/skillsgithub.com/glifxyz/glif-mcp-server
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days 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

flux-3-video

In its own words, on Community GitHub marketplaces:

BFL skills for FLUX 3 video generation including prompt readiness checks, cinematic shot craft for text-to-video, keyframes and video continuation, synchronized audio and dialogue, period and archival format looks, request construction with async polling and downloads, and finished product ads with voiceover and deterministic assembly

Glif

In its own words, on Official MCP Registry:

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

How to run each

flux-3-video As a Claude Code plugin

Claude Code
/plugin marketplace add black-forest-labs/skills
/plugin install flux-3-video@black-forest-labs

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

The marketplaces of flux-3-video publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of flux-3-video publish no settings it asks for, so we do not compare settings.

What it can do: flux-3-video · What it can do: Glif · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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. 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