producer-cue
OfficialRelated Servers
Alternatives to producer-cue
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables AI assistants to generate production-ready, professional UI design systems and components from simple descriptions, with real images, animated components, and automated quality checks.16-
- FlicenseNot gradedqualityCmaintenanceGives AI coding assistants live, structured access to running apps' state and UI elements, enabling real-time verification and interaction across web, mobile, and desktop.36-
- AlicenseAqualityAmaintenanceAI-native design engineering platform that converts Figma or live websites into a semantic design graph for code generation, and generates Figma designs from prompts with a self-improving director loop.2867 npm78MIT

@forgespace/ui-mcpofficial
AlicenseBqualityFmaintenanceEnables AI-driven generation of UI components, full applications, and backend code across multiple frameworks (React, Vue, Angular, Svelte, HTML) with Figma integration and brand identity support.3865 npm2MIT- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, understand, and generate code for design system components by syncing and indexing a component library.-
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents to plan, build, and review websites and product interfaces with a persistent, user-led process, including design direction, component contracts, and implementation review.-
TDQS
Scored across 7 tools
Each tool has a distinct purpose: theme generation, component generation/mutation, auditing/healing, export, primitive retrieval, and Figma sync. However, 'producer_generate_component' and 'producer_get_primitive' might overlap when generating primitives, though one is for full specs and the other for headless primitives.
All tools follow a consistent 'producer_verb_noun' snake_case pattern, with verbs like generate, mutate, audit, export, get, and sync. This is highly predictable and aids in tool selection.
With 7 tools, the server is well-scoped for its purpose: design system production. Each tool covers a critical step in the workflow without redundancy, fitting the ideal 3-15 range.
The core lifecycle of a component (generate, mutate, audit, export) is covered, plus theme and Figma sync. However, there is no tool for deleting components or managing component libraries, and no obvious way to list existing components or themes, which could be a gap.