AWS Diagram vs Glif
AWS Diagram is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-23. 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 |  AWS Diagram |   Glif |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:453d5fc6b50b Forks (GitHub): 1 823 Pulls (Docker Hub): 61 042 Stars (Docker Hub): 1 Stars (GitHub): 9 812 Not marked · First seen |
Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 32 Pulls (Docker Hub): 19 818 Stars (Docker Hub): 2 Stars (GitHub): 215 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 32 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 | AWS Diagram | Glif |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 9 812 (better) | 215 (worse) |
| Pulls (Docker Hub) (differs) | 61 042 (better) | 19 818 (worse) |
| Forks (GitHub) (differs) | 1 823 (better) | 32 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-diagram) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP, stdio |
| Tools it declares (differs) | 3 | 10 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 11 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 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
AWS Diagram
Seamlessly create diagrams using the Python diagrams package DSL. This server allows you to generate AWS diagrams, sequence diagrams, flow diagrams, and class diagrams using Python code.
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
AWS Diagram As a local MCP server: Docker image
claude mcp add --transport stdio aws-diagram -- docker run -i --rm mcp/aws-diagramGlif 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
Only AWS Diagram declares
generate_diagramget_diagram_exampleslist_icons
Only Glif declares
glif_infolist_featured_glifslist_saved_glif_toolsmy_glif_user_infomy_glifsremove_all_glif_toolsremove_glif_toolrun_glifsave_glif_as_toolsearch_glifs
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of AWS Diagram publish no settings it asks for, so we do not compare settings.
What it can do: AWS Diagram · What it can do: Glif · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.