tech-spec vs Glif
tech-spec is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
tech-spec is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. 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-10. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Glif | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.3.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-coder | Removed on 2026-10-23 Version: 0.3.2 Forks (GitHub): 5 Stars (GitHub): 8 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 178 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 | tech-specno longer listed · | Glif |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 8 | 218 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 20 178 |
| Forks (GitHub) (differs) | 5 | 32 |
| 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) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | Not published | 11 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 46 h ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of tech-spec
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system…
-
Agents for system design and architectural thinking.
-
Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.
-
Explore directions through research-led brainstorming, write comprehensive specs, and implement them with risk-first subagent workflows and live verification
-
Save agreed requirements as a durable implementation spec.
-
system-architecture
Agents for system design and architectural thinking.
What each says it does
tech-spec
Writes a typed call-stack architecture handoff: code-shaped contracts plus execution flows, implementation-ready for another engineer. User-invoked only. Not for weighing approaches or deciding the design; use architecture first.
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
tech-spec
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 tech-spec publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of tech-spec publish no settings it asks for, so we do not compare settings.
What it can do: tech-spec · 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.