UI Toolkit MCP Server
Related Servers
Alternatives to UI Toolkit MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes a design system and UX rulebook as tools, enabling AI to generate UI consistent with your design tokens, components, layout rules, accessibility guidelines, and templates. It also provides a review tool to score UI proposals against the design system.-
- FlicenseNot gradedqualityCmaintenanceMCP server for extracting UI components, design tokens, and patterns from websites and generating production-ready React, Vue, and HTML components.-
- FlicenseAqualityDmaintenanceComprehensive MCP server for Fluent UI React v9 development, providing component knowledge, design tokens, code generation, and validation tools.128-
- AlicenseAqualityBmaintenanceDesign system MCP server. 20 tools: extract design tokens from any URL, pull from Figma or Penpot, generate React + shadcn/ui components from specs, run WCAG audits, sync tokens bidirectionally.50214 npm46MIT
- FlicenseNot gradedqualityDmaintenanceA unified MCP server with composable tools for GitHub operations, file management, shell execution, kanban boards, Discord messaging, and package management. Features role-based security, HTTP/stdio transports, and a web-based development UI.-
- AlicenseNot gradedqualityDmaintenanceMCP server for automatic Storybook story generation, component analysis, and validation. Auto-detects React frameworks and syncs component documentation.19 npm1MIT
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes (generation, token management, auditing, layout composition). A few pairs could be confused: audit_component vs live_audit (static markup vs live page) and import_design_tokens vs extract_figma_styles (both load tokens into the store), but the descriptions clearly differentiate them.
Consistent snake_case throughout with a mostly predictable verb_noun pattern (generate_component, import_design_tokens, audit_component, clear_tokens, export_tokens). A handful lean noun-based (visual_diff, live_audit, responsive_preview), a minor deviation but still readable and coherent.
13 tools is well within the ideal 3-15 range and each maps to a distinct capability in the UI workflow (generation, tokens, audit, fix, storybook, layout, visual testing). No filler tools appear present.
The surface covers a broad lifecycle: token import/extract/export/clear, component generation, static and live auditing, auto-fix, storybook generation, responsive preview, visual diff, and layout composition. Minor gaps exist (no explicit component registry/list or delete operations), but core workflows are covered.