hig-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HIG_SOSUMI_BASE | No | Base URL used by the hig_fetch tool. Defaults to https://sosumi.ai; override with HIG_SOSUMI_BASE. | https://sosumi.ai |
| HIG_MCP_CALL_LOG | No | Path to the JSONL file where every tool call is appended. Defaults to $XDG_STATE_HOME/hig-mcp/calls.jsonl; override with HIG_MCP_CALL_LOG. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hig_get_tokensA | Return curated Apple HIG design tokens for a category. Tokens carry provenance: 'src' tags each value (apple-system, apple-hig, figma-effect, community-bestpractice, convention, wcag-aa) and 'verify':true flags values to confirm against the current OS. Semantic colors are dynamic — reference by name, never hardcode hex. Args: params.category: one of color | typography | materials | layout | swiftui | sf_symbols | all Returns: dict: the requested token category (or all categories), as structured data. |
| hig_check_liquid_glassA | Return the Liquid Glass guardrails for a given usage context. Surfaces the budgets agents routinely get wrong — blur radius cap, max compositing layers, contrast-after-blur, depth/frost ranges, and the required reduced-transparency fallback — with provenance so you know which numbers are Apple's vs. community/Figma-derived. Args: params.context: where the material is applied (free text) params.platform: 'iphone' or 'ipad_mac' (selects blur budget) Returns: dict: applicable rules, the platform blur cap, and a checklist. |
| hig_swiftuiA | Map a HIG component to its SwiftUI API plus the token references to apply. Stable APIs are confident; Liquid-Glass-era modifiers are flagged verify:true because names shift between betas — confirm via hig_fetch or Xcode before shipping. Args: params.component: one of the 14 mapped components, e.g. button, tab_bar, sheet (omit to list all) Returns: dict: mapping with swiftui API, token refs, hig_path, and verify flags. |
| hig_fetchA | Fetch current HIG prose as clean Markdown via sosumi.ai. Thin convenience wrapper so this one server covers both tokens and prose. sosumi.ai renders Apple's DocC pages to AI-friendly Markdown. Returned text is for grounding only: summarize and cite the canonical Apple URL, do not reproduce it wholesale. Override the backend with HIG_SOSUMI_BASE. Args: params.path: HIG slug, /design/... path, or full developer.apple.com URL. Returns: dict: markdown content, the sosumi source, and the canonical Apple URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.