About Imagcon
A local MCP server for Imagcon that creates PWA icon sets and iOS splash screens from prompts or existing images. It runs over stdio and calls the Imagcon API, with tools to save, list, and download generated assets.
Key features
- 01Generate source images from prompts
- 02Build icons and splash screens from local images
- 03Create PWA icon packs and manifest.json
- 04Generate 16 iOS splash screens
- 05Save, list, and download asset sets
- 06Check Imagcon credit balance
Use cases
- 01Create installable icon assets for a PWA
- 02Build app icons from an existing image
- 03Generate splash screens for an iOS app
- 04Manage saved icon and splash screen assets
MCP support
The local MCP server connects to the Imagcon API over stdio and exposes tools for image generation, icon and splash screen creation, and asset management to MCP clients.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.imagcon.app/claude mcp add --transport http explorer-64-imagcon https://mcp.imagcon.app/{"mcpServers":{"explorer-64-imagcon":{"type":"http","url":"https://mcp.imagcon.app/"}}}Open in Cursor{"servers":{"explorer-64-imagcon":{"type":"http","url":"https://mcp.imagcon.app/"}}}Open in VS Code{"mcpServers":{"explorer-64-imagcon":{"type":"http","url":"https://mcp.imagcon.app/"}}}{"mcpServers":{"explorer-64-imagcon":{"serverUrl":"https://mcp.imagcon.app/"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://mcp.imagcon.app/Auth requiredTools
Details
From the project READMEimagcon-mcp
Local MCP server that wraps the Imagcon API so assistants can generate PWA icon sets (all sizes, maskable assets, manifest.json) and iOS splash screens without opening the site. Runs as a stdio process via uvx — no hosted service dependency, no persistent connections.
Requirements
- Python 3.11–3.12
- uv (provides
uvx) - An Imagcon API key starting with
ic_live_from imagcon.app/api-keys
Install
The package is self-hosted (not on PyPI). Install directly from the wheel:
claude mcp add imagcon -- uvx --from https://imagcon.app/downloads/imagcon_mcp-0.3.0-py3-none-any.whl imagcon-mcp --api-key ic_live_...
Or with the key in the environment instead of on the command line:
claude mcp add imagcon -- uvx --from https://imagcon.app/downloads/imagcon_mcp-0.3.0-py3-none-any.whl imagcon-mcp
export IMAGCON_API_KEY=ic_live_...
For other MCP clients (Cursor, Windsurf, VS Code, Cline, Zed, Warp, Continue.dev), use the equivalent stdio config:
{
"mcpServers": {
"imagcon": {
"command": "uvx",
"args": ["--from", "https://imagcon.app/downloads/imagcon_mcp-0.3.0-py3-none-any.whl", "imagcon-mcp", "--api-key", "ic_live_..."]
}
}
}
Per-client config file locations and full examples: see CLIENT-CONFIGS in imagcon.app/.well-known/blueprint.txt.
Tools
Images
generate_image— AI-generate a source image from a text description. Returnsimage_keyand a preview URL. Show the preview to the user and confirm before generating icons.save_image— Save a generated image to your gallery byimage_keyandname.list_saved_images— List all saved source images with keys and preview URLs.create_icons_from_key— Generate a PWA install pack from an already-savedimage_key. Returnshtml_head+ a signed ZIP URL; local stdio also extracts tooutput_dir(default./).install_pwa_pack— Same builder ascreate_icons_from_key. Splash is a second credit and defaults to false.
Icon sets
generate_pwa_icons— AI-generate a source image, then a droppablepublic/tree. Extract tooutput_dir(default./). Do not pass./public/icons— that nests.create_pwa_icons_from_image— Same PWA pipeline from an existing local PNG/JPEG/WebP atimage_path(no AI generation).list_saved_icon_sets— List saved icon sets with IDs.download_icon_set— Download a saved icon set ZIP byset_id, extract tooutput_dir.get_icon_set_download_url— Get an authenticated download URL for a saved icon set ZIP byset_id.
Splash screens
generate_splash_screens— AI-generate a source image and produce 16 iOS splash screens, extract tooutput_dir(default./public/splash).create_splash_screens_from_image— Same splash pipeline from an existing local PNG/JPEG/WebP atimage_path(no AI generation).create_splash_screens_from_key— Same splash pipeline from an existingimage_key(e.g. fromgenerate_imageorlist_saved_images) — composites the icon on each canvas size without re-generating.download_splash_screens— Download a saved splash screen set ZIP byset_id, extract tooutput_dir.get_splash_screen_download_url— Get an authenticated download URL for a saved splash screen set ZIP byset_id.
Account
get_credit_balance— Returns remaining Imagcon credits.setup_wallet_profile— Activate a permanent Imagcon account after a pay-per-call x402 payment. Pass wallet address, profile token fromX-Imagcon-Token, name,terms_confirmed(after reading https://imagcon.app/terms-of-service), and a wallet signature overimagcon.app/profile/activate:{profile_token}:{unix_timestamp}.
AI image generation (generate_image, generate_pwa_icons, generate_splash_screens) and icon/splash set exports use credits. create_pwa_icons_from_image, create_splash_screens_from_image, create_splash_screens_from_key, and create_icons_from_key skip AI generation credits but still charge for export.
Configuration
| Source | Variable / flag |
|---|---|
| Environment | IMAGCON_API_KEY |
| CLI | --api-key (overrides the env var) |
If the key is missing, the process exits with an error pointing to imagcon.app/api-keys.
API base URL
All requests go to https://imagcon.app (no other base URL is supported).
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.