Ext Ops Panel
Open dashboard
Comparison

prompt-architect vs Glif

prompt-architect is a plugin bundle for AI coding tools published by Charles Kelsoe. 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-22. 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
Marketplaceprompt-architectGlif
Community marketplace ckelsoe/prompt-architect Listed
Version: 3.5.1
Forks (GitHub): 35
Stars (GitHub): 321
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 32
Stars (GitHub): 215
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:3f93ddceeb99
Forks (GitHub): 32
Pulls (Docker Hub): 19 777
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

prompt-architect vs Glif
Factprompt-architectGlif
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)321 (better)215 (worse)
Pulls (Docker Hub) (differs)No figure on Docker Hub19 777
Forks (GitHub) (differs)35 (better)32 (worse)
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)111
LicenceMITMIT
Repository (differs)github.com/ckelsoe/prompt-architectgithub.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

prompt-architect

In its own words, on Community GitHub marketplaces:

Analyzes and improves prompts using 31 frameworks. Intent-based selection routes to the right framework — from ultra-minimal (APE) to agentic (ReAct).

Glif

In its own words, on Official MCP Registry:

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

How to run each

prompt-architect As a Claude Code plugin

Claude Code
/plugin marketplace add ckelsoe/prompt-architect
/plugin install prompt-architect@prompt-architect-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 prompt-architect publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: prompt-architect · 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