icon-composer-kit
Related Servers
Alternatives to icon-composer-kit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGenerates software and app icons locally as PNG, ICO, or ICNS files with customizable styles, shapes, gradients, text, and shadows, requiring no external APIs or network access.4MIT
- AlicenseAqualityCmaintenanceMCP server for creating Apple .icon bundles with Liquid Glass effects (iOS 26+). 12 tools for programmatic icon creation, glass effect tuning, dark mode, and App Store export.12172 npm53MIT
- AlicenseAqualityDmaintenanceMCP server for searching and exporting Apple SF Symbols as true vector SVGs.41MIT
- AlicenseNot gradedqualityDmaintenanceEnables high-quality conversion of SVG files to PNG, ICO, and JPG formats with optimized Chinese character rendering. Supports single file, batch, and string-based conversions using multiple rendering engines including Cairo, SVGLib, and PIL.MIT
- AlicenseAqualityCmaintenanceRoutes one brief to the right image model across 60+ (gpt-image-1.5, Ideogram 3, Recraft V4, Flux), validates the output, and fans out to iOS/Android/PWA/favicon/visionOS/Flutter bundles. Works without an API key via Pollinations, HF Inference, Stable Horde, or host-LLM inline SVG.2421MIT
- AlicenseNot gradedqualityCmaintenanceGenerates all required web app icons and manifest files from a single source image with framework auto-detection. Supports Next.js App Router, traditional web apps, and PWA standards with zero configuration.13 npmMIT
TDQS
Scored across 6 tools
Each tool targets a distinct action: availability check, list, create, read, update, and render. There is no meaningful overlap or ambiguity between them.
Five tools follow a clear verb_noun snake_case pattern (list_icons, create_icon, read_icon, update_icon, render_icon). composer_status breaks the pattern by being a noun phrase instead of an action-oriented name.
Six tools is well-scoped for an icon composition workflow. Each tool provides a necessary, non-redundant capability without bloat or unnecessary granularity.
The core icon lifecycle of create, read, update, render, and list is covered. A delete or remove operation is missing, and update always creates a new name rather than modifying in place, which may be intentional but leaves a lifecycle gap.