System-agnostic MCP server template for design systems: agents ask for real components, props and tokens instead of guessing
Server has 9 well-named tools with consistent verb_noun patterns (search_, get_, list_, find_, resolve_, check_). All tools have descriptions (avg ~100 chars, within baseline 34-392). Input schemas are present with typed parameters. However, output schemas are not documented in the visible code, parameter descriptions lack detail on constraints/formats, and error handling guidance is absent. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being READ_ONLY. Composition is sound, tools are single-purpose and chainable via 'system' parameter. Missing: enum constraints, format specifications, pagination details, and recovery guidance.
Check if a component or pattern is used correctly in provided code
Find design tokens by name or category, returning token definitions with values and theme variants
Get detailed information about a specific component including props, events, slots, examples, and guidance
Get design guidance and best practices for a component or pattern
Get migration guidance for updating component usage between versions
Get information about design patterns and their component compositions
List all design tokens in a system, optionally filtered by category
Resolve a component name to its exact definition, handling aliases and case-insensitive matching
Output schemas not documented. Tools return structured data but LLMs cannot see field names, types, or which IDs are included for chaining. Violates pattern:tool and mxe:include-chaining-ids.
Parameter descriptions lack format/constraint details. 'query' and 'code' parameters have no guidance on length, format, or examples. Violates pattern:constrained-input and review:param-validation-rules.
No tool annotations despite all tools being READ_ONLY. Missing readOnlyHint in tool definitions. Violates current spec (2026-07-28) tool annotations requirement.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
Search for components in the design system by query string, returning ranked matches with scores and match reasons
No error handling guidance. Tools provide no recovery hints (e.g., 'component not found, try search_components()' or 'invalid query format'). Violates pattern:recovery-guide.
list_tokens lacks pagination parameters (limit, offset, cursor). Large token sets will blow context window. Violates pattern:paginated-result.