Glif vs Losercore Playlist
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). Losercore Playlist is an MCP server published by losercoreplaylist.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 32 Stars (GitHub): 215 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 32 Pulls (Docker Hub): 19 937 Stars (Docker Hub): 2 Stars (GitHub): 215 Not marked · First seen |
Not listed |
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 | Glif | Losercore Playlist |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 215 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 19 937 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 32 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (losercoreplaylist.com/mcp) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 11 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/glifxyz/glif-mcp-server | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-23 |
| Endpoint at the last check (differs) | Responded 44 h ago | not checked yet |
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
Glif
Generate images, video, and audio with Glif's media-generation agent
Losercore Playlist
Search starter tracks, get original scene prompts and prepare free local playlist video projects.
How to run each
Glif As a remote MCP server
claude mcp add --transport http glif https://glif.app/api/mcpLosercore Playlist As a remote MCP server
claude mcp add --transport http creative-tools https://losercoreplaylist.com/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 Losercore Playlist publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Losercore Playlist publish no settings it asks for, so we do not compare settings.
What it can do: Glif · What it can do: Losercore Playlist · Compare two other plugins
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.