Sekura Design MCP
Related Servers
Alternatives to Sekura Design MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceRead-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.83 npmMIT
- AlicenseAqualityCmaintenanceEnables MCP-capable IDEs to search 8,214 design-system components, retrieve exact source bundles and semantic tokens, and follow a copy-first handoff workflow with composition validation.6MIT
- AlicenseAqualityCmaintenanceA design harness for AI coding agents. Better Design gives an agent design systems, UI and UX principles, icons and UI review: it finds or creates a design system that fits the product and installs its components, explains how sign-up, forms and onboarding should work, and reviews finished screens for readability, accessibility and unclear copy.48568MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to access a governed, versioned design style specification through MCP, including deterministic checks, proposal review workflows, and generated CSS, JSON, and TypeScript artifacts.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that provides AI coding agents with a queryable contract for design system tokens, components, patterns, and anti-patterns.24 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to build professional websites using a curated component registry, WCAG-verified design systems and tokens, a human-in-the-loop visual editor, and real-browser Chromium QA that verifies rendered pages and iterates on fixes. It exposes deterministic design decisions, screenshots and evidence-backed quality scores as MCP tools over stdio or Streamable HTTP.Apache 2.0
TDQS
Scored across 21 tools
Most tools have clearly distinct targets (catalogue vs single component vs code vs behaviour vs migration). A few clusters need the descriptions to disambiguate: get_tokens/export_tokens/get_primitives/suggest_token all touch tokens, and validate_markup vs validate_integration overlap on validation. The descriptions do a good job of explaining when to use each, so misselection is unlikely but possible.
Names uniformly follow a snake_case verb_noun pattern (get_component, list_components, validate_markup, export_tokens, audit_theme, suggest_token, check_contrast). The only mild outlier is the bare 'search', which is idiomatic and unambiguous. No mixing of casing or style conventions.
21 tools is on the heavy side but maps to a genuinely broad domain: discovery, components, foundations, tokens, code, patterns, layouts, validation, migration and setup. Each tool earns a distinguishable place, though a few token-related ones could conceivably be consolidated.
Coverage is strong for a read-only design-system surface: overview/discovery, component catalogue and specs, foundations, tokens, code and layout generation, contrast/theme/markup/integration validation, migration and endpoint discovery. Minor gaps like a changelog or version-history tool exist, but core agent workflows have no dead ends.