hig-mcp
Related Servers
Alternatives to hig-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI coding agents to audit Apple HIG compliance across macOS, iPadOS, and iOS, extract multi-format design tokens, compare UI patterns, and scaffold production-ready React/TypeScript components.9MIT
- 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.6416 npm4MIT
- AlicenseAqualityCmaintenanceEnables AI agents to search, retrieve, and navigate Apple's Human Interface Guidelines as live Markdown content across all Apple platforms.4MIT
- AlicenseBqualityFmaintenanceProvides AI assistants with access to Apple's Human Interface Guidelines and technical API documentation across all Apple platforms (iOS, macOS, watchOS, tvOS, visionOS), enabling unified search of design principles and implementation details.23137 npm21MIT
- AlicenseAqualityBmaintenanceA local MCP server that lets AI coding assistants search Apple's Human Interface Guidelines catalog, fetch individual articles as Markdown, and read community implementation notes for native apps and the web. It enables guideline-grounded design, conversion, and auditing workflows across iOS, iPadOS, macOS, watchOS, tvOS, visionOS, and web platforms.6363 npm1MIT
- AlicenseAqualityBmaintenanceLets AI coding tools look up real color palettes—role colors, measured WCAG contrast ratios, and paired usage advice—for App, Web, and Mini App UIs, and export them as ready-to-paste CSS custom properties. It searches a library of 90 palettes by platform, tag, or keyword in English or Chinese, so models stop inventing hex values.4MIT
TDQS
Scored across 4 tools
Each tool has a distinct focal point: prose fetching, SwiftUI component-to-API mapping, Liquid Glass material guardrails, and design tokens. However, hig_fetch and hig_get_tokens both retrieve HIG reference data, and hig_swiftui returns token refs too, so an agent could occasionally conflate them when a request spans prose and tokens.
All tools share a clean 'hig_' prefix, and three use verb_noun style (fetch, check_liquid_glass, get_tokens). hig_swiftui deviates as a noun-only label, and fetch/get are near-synonyms, but overall the pattern is predictable and readable.
Four tools map cleanly onto four distinct concerns (prose, SwiftUI mapping, materials, tokens), so each earns its place with no redundancy. It sits slightly on the lean side for a design-system reference server but is well-scoped for its purpose.
The surface covers prose, tokens, SwiftUI, and Liquid Glass guidance, which is solid core coverage. But it lacks UIKit/AppKit component mappings, only 14 components are mapped, and there is no search or version-scoped lookup, leaving notable gaps for broader design-guideline queries.