Imagcon vs AppLaunchFlow
Imagcon is an MCP server published by Explorer-64. Marketplaces we read that list it: 1 (Official MCP Registry). AppLaunchFlow is an MCP server published by ynnickw. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  Imagcon |  AppLaunchFlow |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.5 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.7.9 Forks (GitHub): 0 Stars (GitHub): 0 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 | Imagcon | AppLaunchFlow |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.imagcon.app) | Remote server (mcp.applaunchflow.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/explorer-64/imagcon-mcp | github.com/ynnickw/applaunchflow-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | Responded 26 h 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
Imagcon
Generate PWA icon sets and iOS splash screens from a text prompt or an existing image.
AppLaunchFlow
Create app-store screenshots, social graphics, promo videos, and animated device mockups.
How to run each
Imagcon 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
AppLaunchFlow As a remote MCP server
claude mcp add --transport http applaunchflow https://mcp.applaunchflow.com/mcpCommands 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 AppLaunchFlow publish no settings it asks for, so we do not compare settings.
What it can do: Imagcon · What it can do: AppLaunchFlow · Compare two other plugins
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.