Sekura Design MCP
Related Servers
Alternatives to Sekura Design MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceRead-only MCP server that exposes a design system's tokens, components, conventions, and deprecations as queryable tools, enabling agents to look up canonical values, assess change impact, and detect hardcoded value drift.81 npmMIT
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server that provides AI coding agents with a queryable contract for design system tokens, components, patterns, and anti-patterns.6 npm1Apache 2.0
- 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.-
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.5 npm9MIT
- AlicenseAqualityFmaintenanceComprehensive MCP server for end-to-end UI development, offering tools to generate components, manage design tokens, audit accessibility, autofix issues, inspect live pages, compare screenshots, and more across multiple frameworks.137 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides resources, tools, and prompts for a Design System via MCP protocol, enabling component search, reading, and related component discovery.205 npmMIT
TDQS
Scored across 19 tools
Most tools cleanly map to distinct resources or actions, and the consistent prefixes make routing straightforward. The only real ambiguities are validate_integration vs validate_markup and get_tokens vs export_tokens, but their descriptions clarify the different intents.
The set overwhelmingly follows a snake_case verb_noun pattern such as get_component, export_tokens, and audit_theme. The single bare verb 'search' is a minor deviation from an otherwise uniform convention.
At 19 tools, the surface sits in the 16–25 range that feels heavy for agent navigation, even though the design-system domain is broad. The tools are largely non-redundant, so the count is borderline rather than excessive.
The server covers discovery, retrieval, validation, export, and integration setup with no obvious dead ends for a read-only design-system knowledge and validation server. get_overview ties the surface together and points to every relevant tool.