Prompt-to-asset
MCP server that generates production-ready visual assets by routing requests across 30+ image generation models. Handles app icons, favicons, OG images, logos, and wordmarks. Validates output for WCAG contrast and palette consistency. Zero API key required for first run via Pollinations and Stable Horde free tiers.
Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Canonical URL
- https://heyclau.de/entry/mcp/prompt-to-asset
- Source URLs
- https://github.com/MohamedAbdallah-14/prompt-to-asset#readme, https://github.com/MohamedAbdallah-14/prompt-to-asset
- Safety notes
- Review generated assets, licensing, and usage rights before publication, and avoid sending confidential brand or source material.
- Privacy notes
- Prompts, uploaded or reference images, brand specifications, and generated assets may be sent to external model providers.
- Author
- MohamedAbdallah-14
- Submitted by
- MohamedAbdallah-14
- Original submission
- https://github.com/JSONbored/awesome-claude/issues/305
- Reviewed by
- JSONbored
- Claim status
- unclaimed
- Last verified
- 2026-04-25
Safety notes
- Review generated assets, licensing, and usage rights before publication, and avoid sending confidential brand or source material.
Privacy notes
- Prompts, uploaded or reference images, brand specifications, and generated assets may be sent to external model providers.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
Full copyable content
claude mcp add prompt-to-asset -- npx -y prompt-to-assetAbout this resource
Overview
Prompt-to-asset is an MCP server that turns text prompts into production-ready visual assets — app icons, favicons, OG images, logos, and wordmarks — by routing each request across 30+ image generation models and selecting suitable output. It validates results for WCAG contrast and palette consistency, so generated assets are usable rather than just decorative. No API key is required for the first run: it falls back to the Pollinations and Stable Horde free tiers.
Setup
Add it to Claude Code with one command:
claude mcp add prompt-to-asset -- npx -y prompt-to-asset
Or register it directly in your MCP client config:
{
"mcpServers": {
"prompt-to-asset": {
"command": "npx",
"args": ["-y", "prompt-to-asset"]
}
}
}
What it generates
- App icons and favicons in standard sizes
- Open Graph and social share images
- Logos and wordmarks
- Palette- and contrast-checked variants (WCAG)
Safety & privacy
Review generated assets, licensing, and usage rights before publishing, and avoid sending confidential brand or source material. Prompts, reference images, brand specifications, and generated assets may be sent to external model providers.
Source citations
- Source repositorygithub.com 2026-04-30T11:16:21.000Z
- Documentationgithub.com
- Reviewed by JSONbored2026-04-30T11:16:21.000Z
- Submitted by MohamedAbdallah-142026-04-25T15:44:14.000Z
Add this badge to your README
How it compares
Prompt-to-asset side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | MCP server that generates production-ready visual assets by routing requests across 30+ image generation models. Handles app icons, favicons, OG images, logos, and wordmarks. Validates output for WCAG contrast and palette consistency. Zero API key required for first run via Pollinations and Stable Horde free tiers. Open dossier | MCP server and CLI for AI image and video generation with gallery search, prompt enhancement, model listing, local preferences, ComfyUI workflows, MeiGen Cloud, and OpenAI-compatible provider support. Open dossier | MCP server and Agent Skill from better-auth for searching, recommending, retrieving, batching, and syncing Iconify-powered SVG icons from 200,000+ icons across 150+ collections. Open dossier | Source-install MCP server for controlling a local ComfyUI instance so Claude can generate, view, regenerate, manage, and publish image, audio, and video assets through workflow-backed tools. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | MohamedAbdallah-14 | MeiGen | better-auth | Joe Norton |
| Added | 2026-04-25 | 2026-06-06 | 2026-06-18 | 2026-06-06 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Review generated assets, licensing, and usage rights before publication, and avoid sending confidential brand or source material. | ✓MeiGen can submit image and video generation jobs to external providers or a local ComfyUI backend. Image and video generation may spend credits, use paid APIs, or consume local GPU resources depending on the configured provider. Local reference images can be compressed and uploaded through the configured upload gateway before being sent to API providers. Video generation can take minutes, may time out at the MCP client, and should not be retried blindly because jobs or credits may already be in progress. ComfyUI workflow import and modification can run local workflows; review workflow JSON and custom nodes before use. | ✓Better Icons can write icons into a project file through `sync_icon`; review the target path, component name, framework, and diff before committing generated code. Icon output can include raw SVG, JSX/component usage, URLs, or generated project code. Review SVG attributes and generated code before use in production UI. Learned preferences and recent icons can influence future recommendations; clear preferences when switching projects or style systems. Batch retrieval can add many icons quickly. Keep requested sets bounded and avoid mixing unrelated icon styles in a shared design system. | ✓ComfyUI MCP Server can submit prompts and workflows to a local ComfyUI instance, create generated media, poll jobs, cancel jobs, and publish assets into project directories. Generated images, audio, and video can contain unsafe, infringing, biased, misleading, or policy-sensitive content depending on prompts, models, LoRAs, and workflows. Publishing tools can copy, compress, convert, overwrite, and update manifest entries for assets, so verify target filenames and directories before use. Custom workflows can expose arbitrary parameters and may run heavy GPU workloads or fail if nodes, models, or paths are missing. Keep the server bound to local trusted clients unless you have added appropriate authentication and network controls. |
| Privacy notes | ✓Prompts, uploaded or reference images, brand specifications, and generated assets may be sent to external model providers. | ✓API tokens, OpenAI-compatible credentials, provider base URLs, upload gateway URLs, ComfyUI URLs, preferences, recent generations, prompts, model IDs, and output paths can reveal private creative workflows. Uploaded reference images may become public URLs through the configured upload gateway before generation. Prompts, reference images, generated image URLs, generated video URLs, saved outputs, and favorite prompts can contain client work, brand plans, product images, personal likenesses, or unreleased campaigns. Keep secrets in MCP client environment configuration, review generated media before sharing, and remove local outputs when retention is no longer needed. | ✓Icon search queries, selected icon IDs, preferred collections, recent icons, target icon file paths, framework names, and generated SVG/component code may be visible to the MCP client and model provider. `sync_icon` can expose local project structure and icon-file conventions to the agent. Avoid sending private product names, unreleased feature labels, customer-specific UI terms, or proprietary design-system names in icon search prompts when that context is sensitive. | ✓Prompts, negative prompts, generated media, workflow parameters, model names, job IDs, asset metadata, and publish paths can appear in MCP responses, logs, and model transcripts. Generated assets may be stored in ComfyUI output folders, the MCP asset registry, project publish directories, or manifests. Do not feed private images, brand assets, customer materials, or regulated media into workflows unless the local model environment is approved for that data. Review model and workflow licenses before publishing or redistributing generated assets. |
| Prerequisites | — none listed |
|
|
|
| Install | | | | |
| Config | | | | |
| Citations |
| |||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Related guides
Source-backed guides for putting this to work.
Auditing MCP Client Configuration Before Team Rollout
Audit MCP client configuration before sharing it with a team.
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.