"Ant Design" matching MCP servers:

Provides access to Ant Design component library documentation and information for automated code generation. Enables searching components by category or keyword, retrieving component props, examples, API documentation, and available icons.

Exposes Ant Design component documentation to Large Language Models, allowing LLMs to explore and understand Ant Design components through specialized tools for listing components, viewing documentation, inspecting props, and browsing code examples.

Fetches and structures Ant Design v4 component documentation into JSON format, enabling AI agents to search, analyze, and retrieve component metadata, APIs, and examples.

Provides AI assistants with comprehensive Ant Design component documentation, examples, API references, and best practices. Supports multiple versions and enables natural language queries for React UI component development.

Enables AI agents to manage routes on the Design Canvas infinite canvas app, including adding, removing, listing routes, and capturing screenshots of the canvas.

Design contract layer for AI agents. Scans Figma, code, Storybook, and token files, reconciles conflicts, and serves a single machine-readable source of truth so every agent gets the same authoritative design rules before it builds. Local-first.

Manages design tokens (colors, spacing, fonts) in a JSON file and enables agents to read, write, export, and detect drift between tokens and CSS via MCP.

A read-only MCP server for reading and analyzing Lanhu (Blue Lake) design projects, providing tools to retrieve design lists, previews, node trees, schemas, and exportable resources.

Enables AI coding agents to retrieve mode and stage guidance so they can lead users through a 9-stage design workflow, including questions, required artifacts, exit criteria, dependencies, pitfalls, rollback impact, and environment requirements. It helps non-designers turn ideas into buildable HTML/WPF design specs while keeping the human in control of confirmation and revisions.

AI Design Blueprint is a doctrine and runtime standard for agentic AI: 10 principles, 16 laws, and Pro/Teams validators your coding agent calls over MCP.

An unofficial MCP server that gives AI assistants structured access to Italy's Design System .italia, including components, design tokens, usage guidelines, and GitHub issues, updated nightly.

Enables high-craft web design and engineering through OKLCH color systems, fluid typography, Three.js 3D scenes, frontend security audits, multi-viewport capture, and Python-backed design verification.

Enables bug localization by analyzing a repo and bug report with an ant-swarm LLM, returning a HOT/WARM/COLD heatmap and JSON audit trail via MCP.

Provides software design guidance via MCP, including SOLID principles, design patterns, pattern scaffolding, and heuristic code-smell detection to help review and refactor code.

Enables AI coding agents to search public design-system catalogs and retrieve only the relevant tokens or sections for a chosen brand, so generated UI matches a specified visual style instead of generic AI output.

Provides design pattern templates and anti-pattern guidance to AI coding agents for correct pattern implementation.

Converts a Figma file into a React project using Ant Design, AG Grid, ApexCharts, and Tailwind CSS, with optional export of mobile screens as a React Native (Expo) app.

Enables assistants to discover, search, and extract real design systems — palettes, type scales, spacing, surfaces, and do/don't guidance — from the public style pages of styles.refero.design. It reports index coverage with every search and renders matched styles as structured design.md sections or parsed JSON tokens.

Provides comprehensive UI design assistance tools for LLMs, generating color palettes, typography, spacing systems, shadows, design tokens, and more via the MCP protocol.

A local stdio MCP server that enables AI coding tools to search and retrieve reusable interactive and motion design parts from a design-notes library, returning each part's notes, anchors, extracted parameters, and the absolute path to its self-contained index.html source. It also serves the original README provenance and source URLs for a given note.