@lando-labs/lando-ds-mcp
OfficialRelated Servers
Alternatives to @lando-labs/lando-ds-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for the coss ui design system, enabling AI agents to fetch components, props, and design tokens on demand for accurate, low-cost code generation.61MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.5 npm9MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.1MIT
- FlicenseBqualityDmaintenanceAutomated MCP server for the Insider Design System. Enables AI assistants to discover, understand, and generate code for over 60 Design System components with automated extraction from source code.14-
- AlicenseNot gradedqualityCmaintenanceMCP server for design tokens that gives AI agents read access to design systems, enabling token resolution, listing, and component usage lookups via natural language.Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that enables AI to interact with the private 'my-design' React component library and design tokens for UI generation and technical support. It provides tools for component searching, API documentation retrieval, and migration guidance based on specific internal design specifications.6MIT
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes: listing vs. getting vs. composing. However, get_component_reference bundles props and composition hints, which overlaps with get_component_props and get_composition_hints. Agents might be uncertain whether to use the full reference or the targeted sub-tools, but descriptions help disambiguate.
All tool names follow a consistent snake_case verb_noun pattern: list_*, get_*, compose_*, search_*. Even the multi-word names like get_component_reference and get_ds_metadata are predictable and logically structured.
15 tools is within the ideal 3-15 range and is appropriate for a design system server. Each tool covers a distinct aspect (components, tokens, icons, hooks, metadata) without feeling bloated or redundant.
The tool surface is remarkably complete for a read-only design system domain: component discovery, code generation, prop introspection, composition, tokens, animations, icons, themes, hooks, and metadata. No obvious gaps that would cause agent failures.