asset-generator vs Imagcon
asset-generator is a plugin bundle for AI coding tools published by Blueprint-Studio-AI. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Imagcon is an MCP server published by Explorer-64. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  asset-generator |  Imagcon |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.5 Forks (GitHub): 0 Stars (GitHub): 2 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 | asset-generator | Imagcon |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (tools.blueprintstudio.ai/api/mcp) | Remote server (mcp.imagcon.app) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/blueprint-studio-ai/claude-code-asset-generator | github.com/explorer-64/imagcon-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 6 days ago, requires a key | Responded 4 days ago, requires a key |
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
asset-generator
Generate production-ready visual assets without leaving your terminal. Describe what you need in plain English: icons, illustrations, placeholders, and Blueprint Studio generates them in your brand's style and saves them to your project. Manage brands, invite teammates, create custom styles, and automate with API keys. Browser-based auth, no keys to copy.
Imagcon
Generate PWA icon sets and iOS splash screens from a text prompt or an existing image.
How to run each
asset-generator As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install asset-generator@claude-communityImagcon As a remote MCP server
claude mcp add --transport http imagcon-mcp https://mcp.imagcon.app/ --header "Authorization: Bearer <YOUR_IMAGCON_API_KEY>"Requires: IMAGCON_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of asset-generator publish no settings it asks for, so we do not compare settings.
What it can do: asset-generator · What it can do: Imagcon · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.