@lando-labs/lando-ds-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@lando-labs/lando-ds-mcp list all button components"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@lando-labs/lando-ds-mcp
MCP server for the Lando Labs Design System. Gives AI agents authoritative introspection and code-generation for 127 React components, 19 utility hooks, 70 brand icons, ~1,500 Lucide icons, six token categories, and multiple theme presets — all sourced from the DS's own emitted metadata (@lando-labs/lando-ds-meta), always current with each DS release.
Built on the Model Context Protocol. Works with Claude Code, Claude Desktop, Cursor, Windsurf, Zed, and any MCP-compatible client.
What it does
Exposes 15 tools to any MCP-connected AI client:
Tool | Purpose |
| Enumerate DS components, filter by category / capability / deprecation |
| Generate ready-to-use JSX for a component with props, children, and correct imports |
| TypeScript-style props interface for any component |
| Full reference: description + examples + composes + props in one call |
| Capability matrix — RSC-safe, polymorphic, forwardRef, deprecated |
| Which components officially compose with a given one (from meta) |
| Merge multiple components into one snippet with unified imports |
| Design tokens (colors, spacing, typography, radius, shadows, motion) in CSS, hex, or both |
| Curated animation patterns with CSS keyframes and reduced-motion handling |
| Available theme presets (default |
| Browse icons: |
| Semantic search across icon catalogs with confidence-ranked results |
| Enumerate DS utility hooks (state, dom, browser, a11y, …), filter by category / RSC safety |
| Full detail for a single hook — signature, returns, RSC safety, subpath, description |
| DS package version, meta schema version, component/token/icon/hook summary |
Every tool reads from @lando-labs/lando-ds-meta — the DS's self-describing metadata, shipped as a zero-dependency JSON npm package. When the DS ships new components, deprecates old ones, or renames tokens, the MCP surfaces the change on the next content refresh with zero code changes.
Related MCP server: ds-pilot
Install + connect
You need Node.js 18 or later.
Claude Code
npm install -g @lando-labs/lando-ds-mcp
claude mcp add lando-ds lando-ds-mcpOr via ~/.claude.json:
{
"mcpServers": {
"lando-ds": {
"command": "lando-ds-mcp"
}
}
}Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows/Linux:
{
"mcpServers": {
"lando-ds": {
"command": "npx",
"args": ["-y", "@lando-labs/lando-ds-mcp"]
}
}
}Restart Claude Desktop after saving.
Cursor
Edit ~/.cursor/mcp.json:
{
"mcpServers": {
"lando-ds": {
"command": "npx",
"args": ["-y", "@lando-labs/lando-ds-mcp"]
}
}
}Windsurf
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"lando-ds": {
"command": "npx",
"args": ["-y", "@lando-labs/lando-ds-mcp"]
}
}
}Zed
Zed uses context servers configured via ~/.config/zed/settings.json:
{
"context_servers": {
"lando-ds": {
"command": {
"path": "npx",
"args": ["-y", "@lando-labs/lando-ds-mcp"]
}
}
}
}Generic MCP client
The server speaks MCP over stdio. Invoke lando-ds-mcp (after npm install -g) or npx @lando-labs/lando-ds-mcp.
Verify
After connecting, ask your agent to call get_ds_metadata. It should reply with the DS version, component count, and tool summary. If it does, you're wired up.
What it does not do
Not a UI library. The MCP tells agents about DS components — the actual components live in
@lando-labs/lando-dsand must be installed in your project separately.Not a code generator standalone. Runs as an MCP server; needs an MCP client to invoke it.
Not a project scanner. Every tool reads from DS meta; nothing scans your project source. A future release may add DS-adoption auditing tools; not yet.
Not Vue/Svelte/Angular compatible. The DS is React; the MCP's code-generation output is JSX.
Not React Native compatible. The DS is web-only as of v0.57.0.
How it works
The DS publishes @lando-labs/lando-ds-meta — a zero-dependency npm package with meta.json (light) and meta.verbose.json (with descriptions, examples, and composition hints). The MCP takes a semver dep on it and exposes the data through the 15 tools above. npm update @lando-labs/lando-ds-meta is the whole content-refresh workflow.
Because meta is the source of truth, the MCP is a thin protocol adapter over emitted metadata — no synthesis of information the DS didn't emit.
Contributing
Contributions welcome — file an issue or open a PR. Some context up front:
Development setup:
git clone, thennpm install && npm run build && npm test. Nothing else — DS meta arrives via npm.Meta compatibility: MCP consumes DS meta schema
^1.x. Schema major bumps require an MCP major bump.Testing:
npm testuses a custom runner insrc/test.ts.Version discipline: version strings live in
package.json,src/index.ts, andCHANGELOG.md. The version-sync tests fail CI if these drift.
Issues: github.com/lando-labs/lando-ds-mcp/issues Security disclosures: see MAINTAINERS.md. Maintainers: MAINTAINERS.md.
License
Apache License 2.0. See LICENSE for full terms and NOTICE for attribution.
Copyright 2026 Lando Labs.
Related
@lando-labs/lando-ds — The design system itself. React web components; the source of truth the MCP reflects.
@lando-labs/lando-ds-meta — Zero-dependency JSON metadata subpackage the MCP consumes at runtime. Updating the MCP's DS content is
npm update @lando-labs/lando-ds-meta.
First published to public npm and public GitHub as @lando-labs/lando-ds-mcp@4.0.0 on 2026-07-16, alongside @lando-labs/lando-ds@0.57.0 and @lando-labs/lando-ds-meta@0.57.0.
Available Tools
15 toolscompose_componentsA
Compose multiple DS components into a single snippet with a merged import block. Refuses composition if any component is not in DS meta.
Inputs: components (required).
get_animation_examplesB
Canonical DS animation patterns (CSS keyframes + usage). Brand-neutral.
Inputs: animationType.
get_componentA
Generate a JSX snippet (import + element) for a DS component with the given props/children. Rejects JSX-unsafe prop values.
Inputs: componentName (required), props, children.
get_component_capabilitiesA
DS capability introspection. Full matrix by default; pass filters (rscSafe, clientOnly, polymorphic, withRef, deprecated) or component for a single entry.
Inputs: rscSafe, withRef, component, clientOnly, +2 more.
get_component_propsA
Return a TypeScript-interface view of a component's props, derived from meta.components[X].props.
Inputs: componentName (required).
get_component_referenceA
Full component reference in one call — description, examples, composition hints, props, and (optionally) theming class-name maps. Replaces v2.x get_component_docs + get_usage_example.
Inputs: componentName (required), include.
get_composition_hintsA
DS-authoritative composition hints for a component — for each documented prop, which component (or shape) it expects. Sourced from meta.verbose.composes.
Inputs: componentName (required).
get_design_tokensA
DS design tokens (colors, spacing, typography, radius, shadows, motion). format: css (default, CSS var references — resolve to OKLCH at runtime), hex (sRGB hex from meta), or both.
Inputs: format.
get_ds_metadataA
One-call "what am I talking to" — DS package name/version, meta schema version, component/capability/icon/hook totals, exports map. Useful for CI version guards and self-orientation.
Inputs: no named parameters.
get_hookA
Full detail for a DS utility hook — signature, returns, category, RSC safety, subpath, description, and an import snippet.
Inputs: hookName (required).
get_theme_presetsA
Available DS theme presets. Post-v0.34 brand-neutralization: consumers pick a preset (or apply their own ramps) rather than getting a baked brand default.
Inputs: no named parameters.
list_componentsA
List DS components with optional filters (category, deprecated, serverSafe, polymorphic, kind). Meta-backed since v3.0.0.
Inputs: kind, category, deprecated, serverSafe, +1 more.
list_hooksA
List DS utility hooks (state, dom, browser, a11y, etc.) with optional filters (category, serverSafe). Meta-backed since v3.3.0 (DS meta schema 1.3).
Inputs: category, serverSafe.
list_iconsA
List available icons. source: "ds-brand" = DS-authoritative brand icons (from meta.icons.registry, ~70). source: "lucide" = the full Lucide catalog (~1,500); ~80 have hand-authored metadata, the rest are exposed by name + import example. source: "all" unions both.
Inputs: limit, query, source, category.
search_iconsB
Semantic icon search by purpose. Searches across DS-brand + full Lucide catalog; metadata-annotated icons rank higher (richer signal), bare Lucide names still match via name similarity.
Inputs: query (required), limit, source, category.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Live React design-system APIs, patterns, and code validation so AI agents build real UI, not slop.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Related MCP Servers
- 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
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.4 npm9MIT
- 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-
- 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