Ext Ops Panel
Open dashboard
Comparison

design-discussion vs Glif

design-discussion is a plugin bundle for AI coding tools published by sunagaku. 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-11-09. 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
Marketplacedesign-discussionGlif
Community marketplace sean-sunagaku/claude-code-plugin Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 38
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 162
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

design-discussion vs Glif
Factdesign-discussionGlif
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)38 (worse)218 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub20 162
Forks (GitHub) (differs)1 (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)611
LicenceMITMIT
Repository (differs)github.com/sean-sunagaku/claude-code-plugingithub.com/glifxyz/glif-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-11-052026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 24 h 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

design-discussion

In its own words, on Community GitHub marketplaces:

「こんな機能を作りたい」「この設計どうしよう」という技術的な意思決定を、 5人の専門エージェントチームで壁打ちするスキル。 実装アプローチの比較・技術設計の選択・アーキテクチャの意思決定に特化。 Use when: 複数の実装方法があって迷っている時、設計の良し悪しを議論したい時、 技術的トレードオフを整理したい時。 Triggers: "設計壁打ち", "design discussion", "どう設計すべき", "実装アプローチを比較", "アーキテクチャ相談", "設計どうしよう", "技術選定したい", "ADR を作りたい", "設計の議論", "技術的トレードオフ"

Glif

In its own words, on Official MCP Registry:

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

How to run each

design-discussion As a Claude Code plugin

Claude Code
/plugin marketplace add sean-sunagaku/claude-code-plugin
/plugin install design-discussion@sunagaku-marketplace

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 design-discussion publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of design-discussion publish no settings it asks for, so we do not compare settings.

What it can do: design-discussion · 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