MCP server

Design Systems MCP Server: A Cited Knowledge Base for Agents

The Design Systems MCP server gives an AI coding agent a hosted knowledge base of 395 curated entries on design system practice, standards and agent-interface protocols.

Run
claude mcp add --transport http design-systems https://design-systems-mcp.southleft.com/mcp
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the Design Systems MCP server?

Design Systems MCP is a hosted knowledge server with 395 curated entries covering W3C standards, WCAG, major design systems and newer agent-interface protocols. Five tools let an AI coding agent search, browse by category or tag and fetch cited passages, with no local install needed.

It is a Model Context Protocol server that provides access to design systems knowledge. The README counts 395 curated entries: W3C standards, WCAG 2.2, ARIA practices, major design systems and the 2025 to 2026 agent-interface protocols.

The README's argument is that model training goes stale on fast-moving specs. This server serves dated, cited, extracted primary-source content, so an agent answers from sources instead of from memory.

What changes in your agent's output

  • Answers about tokens, accessibility and component architecture come with source reliability labels such as primary, authoritative or community.
  • Search uses vector and keyword matching, with a relevance floor so an uncovered topic returns nothing rather than adjacent filler.
  • Major systems, such as Carbon, Polaris, Material 3 and shadcn/ui, are covered for guidance and token architecture, not only props.
  • Content on agent-facing design layers such as AGENTS.md, SKILL.md and DESIGN.md is included.

How the setup works

  1. Point your client at the hosted endpoint. No installation is needed.
  2. Or run the server locally from the repository for development.
  3. Ask a design system question and let the agent call the search tools.

Who the Design Systems MCP server is for

Best for

  • Design system teams that want agents to cite standards instead of guessing, alongside web design guidelines checks.
  • Builders documenting tokens and component contracts, who may also use Story UI for stories.
  • Anyone comparing design system practice across vendors before choosing an approach.

Not for

  • Reading or editing a design file. The Figma MCP server and the Penpot MCP server do that.
  • Offline use. The recommended path is the public hosted endpoint.
  • Generating components. It returns knowledge, not code.

Use it with UiChemy

The server informs how an agent reasons about design systems. For WordPress output, UiChemy builds the pages: Figma to WordPress turns a design into editable blocks, and Composer edits them inside Elementor or Gutenberg. Click Get Started on uichemy.com.