MCP server

prompt-to-asset MCP: Routed Image Generation for Developers

prompt-to-asset MCP turns one brief into logos, app icons, favicons and OG images, routing across 30 plus image models and validating every output before it ships.

Run
claude mcp add prompt-to-asset -- p2a
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is prompt-to-asset MCP?

prompt-to-asset is a stdio MCP server and CLI that turns a one-line brief into app icons, favicons, OG images, logos, splash screens and SVG art, exported for iOS, Android, PWA and more. It routes across more than 30 image models, tries free routes first, and validates dimensions, alpha and contrast before handing back a bundle.

It is a stdio MCP server, packaged with its own CLI, that turns a one-line brief into production assets: logos, app icons, favicons, OG images, illustrations and splash screens. The same 24 tools back both surfaces, so a CI script and a chat assistant hit identical code.

The three generation modes

  • inline_svg has the host model write SVG directly, then asset_save_inline_svg validates it and writes the bundle, no provider key needed.
  • external_prompt_only returns a ranked, free-first paste target, then asset_ingest_external mattes, vectorizes and validates whatever comes back.
  • api calls a routed provider directly, zero-key via Cloudflare Workers AI, NVIDIA NIM, HF Inference or Stable Horde, or a paid key if one is set.

What zero-key first means

asset_enhance_prompt ranks free routes ahead of paid ones on every call: Cloudflare Workers AI, NVIDIA NIM, HF Inference and Stable Horde cover diffusion models, and Pollinations needs no signup at all. A paid key only gets used when a job specifically calls for it.

What validation checks before shipping

asset_validate runs tier-0 checks on every output: pixel dimensions, alpha channel presence, a checkerboard FFT that catches a fake transparent background rendered as pixels, a safe-zone bounding box, ΔE2000 palette drift against the brand, WCAG contrast and OCR Levenshtein distance on any wordmark text.

Who prompt-to-asset MCP is for

Best for

  • Developers who want an app icon, favicon or OG image bundle without picking an image model or opening a billing console first.
  • CI pipelines that need the same asset generation the chat assistant uses, since the CLI and the MCP tools share one core.
  • Teams that want shipped assets checked for a transparent-background failure or contrast problem before a release, not after a bug report.

Not for

  • When the input is already a finished SVG that needs Android Vector Drawable XML output instead of a new generated asset, the SVG to Android Vector converter is the better fit for that single conversion.
  • When the deliverable is one animated SVG rendered from a JSON config with a PNG preview, rather than a routed production asset bundle, nakkas MCP Server is the better fit for that render.
  • When the need is loading general visualization design guidelines for charts or mockups on demand rather than generating a finished asset bundle, Generative UI MCP is the better fit for that guidance.
  • When the job is producing mockups, icons and illustrations with prompt patterns, a curation loop and brand compliance scoring rather than routing across image models directly, the AI Design Generation skill is the better fit for that process.