A
licenseNot graded
qualityB
maintenanceEnables coding agents to retrieve accurate design system information, component APIs, design tokens, and coding standards, so they build with real specs rather than guessing.
2
MIT
melta-ds-mcp
by tsubotax
Related Servers
Alternatives to melta-ds-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a workspace's design system before writing UI and validate generated code against the same system afterward, using configurable token and component sources.9 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a real API for coding agents to look up design system components, props, and tokens, preventing guessed answers.7MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to score live URLs against a 40-check design contract, validate DTCG tokens and Lottie animations, audit accessibility, and retrieve design-system contracts, catalogs, and review rubrics.35 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to access design system tokens and component contracts through MCP, reducing token usage and ensuring consistency.29MIT
- AlicenseAqualityBmaintenanceProvides deterministic, read-only design knowledge for AI coding agents to help them choose visual directions, plan UI states, and compose design tokens, all without network access.612 npm4MIT
TDQS
A3.8/5.0
Scored across 6 tools
Disambiguation4/5
Most tools target distinct objects (get_component, get_token, search) with clear boundaries, but check_rule, check_html, and get_rules form a cluster around prohibition rules. The descriptions do distinguish them (apply to class strings vs. full HTML vs. retrieve raw rules), so an agent can reasonably select correctly.
Naming Consistency4/5
Names mostly follow a verb_noun pattern (get_component, get_token, get_rules, check_rule, check_html), with only 'search' as a bare verb deviation. Still highly predictable and consistent in style.
Tool Count5/5
Six tools is well-scoped for a design-system lookup and validation server. Each tool serves a distinct purpose (component metadata, tokens, search, three rule-checking variants) with no obvious filler.
Completeness4/5
The surface covers the core read-only lifecycle: discover (search), inspect (get_component/get_token), and validate (check_rule/check_html/get_rules). Only minor gaps exist, e.g. no explicit list-components or list-tokens endpoint, though search largely covers discovery.
Maintenance
ActivityActive
ResponsivenessUnresponsive