TDPilot vs Glif
TDPilot is a plugin bundle for AI coding tools published by silviu. 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-20. 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 | ||
|---|---|---|
| Community marketplace dreamrec/tdpilot | Listed Version: 2.4.1 Forks (GitHub): 1 Stars (GitHub): 15 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 36 Stars (GitHub): 215 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 36 Pulls (Docker Hub): 19 759 Stars (Docker Hub): 2 Stars (GitHub): 215 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 | TDPilot | Glif |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 15 (worse) | 215 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 19 759 |
| Forks (GitHub) (differs) | 1 (worse) | 36 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | 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) | 6, secrets among them: 2 | 3, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 19 | 11 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/dreamrec/tdpilot | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 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
TDPilot
TDPilot v2.4 routes exact validated patterns through deterministic planning and artistic or multi-domain requests through grounded concept authoring, then requires complete intent coverage before transactional execution. Live graph, runtime, visual, and performance checks plus bounded repair prevent partial scaffolds from being called finished. Local-first, 114 MCP tools, no signup or hosted model dependency.
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
TDPilot As a Claude Code plugin
/plugin marketplace add dreamrec/tdpilot
/plugin install tdpilot@dreamrec-TDPilot
Glif As a remote MCP server
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 TDPilot publish no list of tools, so we do not compare tools.
Settings each asks for
Only TDPilot asks for
TD_MCP_AUTOGENERATE_SECRET (secret)TD_MCP_EXEC_MODETD_MCP_HOSTTD_MCP_PORTTD_MCP_REQUIRE_AUTH (secret)TD_MCP_WS_PORT
Only Glif asks for
GLIF_API_TOKEN (secret)GLIF_IDSIGNORE_SAVED_GLIFS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: TDPilot · 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.