Acme Design System
Allows the server to consume static Markdown files as documentation or pattern content.
Allows the server to read MDX documentation folders to provide component and pattern guidance.
Allows the server to ingest Notion exports as a source for patterns and documentation.
Allows the server to use Storybook metadata to provide component discovery, documentation, and usage guidance.
Allows the server to run Stylelint-based review checks for CSS compliance.
Click 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., "@Acme Design SystemWhat are the accessibility guidelines for the Button component?"
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.
Design System MCP Kit
Generic scaffold for teams building an MCP server that exposes their design system to AI agents.
Inspired by GitHub Primer's @primer/mcp, but split into:
@ds-mcp/core— reusable framework (tools, registry, adapter contracts)examples/acme-ds-mcp— minimal working implementation teams can copy
Why this exists
Primer solved a specific problem well: give AI agents authoritative design-system context instead of hallucinating components, tokens, or accessibility rules.
Most design teams need the same capability, but their sources differ:
Storybook metadata vs generated JSON vs TypeScript manifests
Figma tokens vs Style Dictionary vs CSS variables
Local MDX docs vs remote documentation sites
Custom lint rules vs Stylelint presets
This kit standardizes the MCP tool surface and lets each team plug in adapters for their own data sources.
Related MCP server: Design System MCP Server
Architecture
flowchart TB
Agent[AI Agent / Cursor / Copilot]
Client[MCP Client]
Server[Your DS MCP Server]
Core["@ds-mcp/core"]
Adapters[Team Adapters]
Sources[(Components / Tokens / Docs / Icons)]
Agent --> Client --> Server --> Core
Server --> Adapters --> SourcesLayers
Layer | Responsibility | Team customizes? |
MCP transport | stdio server, client wiring | Rarely |
Tool registry | Standard tool names + handlers | Enable/disable tools |
Adapters | Read design-system knowledge | Yes — main work |
Snapshots | Bundled fallback catalog | Optional bootstrap |
Standard tools (Primer-compatible surface)
Category | Tools |
Setup |
|
Components |
|
Patterns |
|
Tokens |
|
Icons |
|
Foundations |
|
Review |
|
Tools auto-register only when the required adapter is present.
Quick start
npm install
npm run build
npm run example:acmeCursor / VS Code MCP config
{
"servers": {
"Acme Design System": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/design-system-mcp-kit/examples/acme-ds-mcp/dist/index.js"]
}
}
}How teams adopt this
Phase 1 — Snapshot bootstrap (1–2 days)
Copy
examples/acme-ds-mcptopackages/your-ds-mcpReplace
data/catalog.snapshot.jsonwith your component/token/icon inventoryUpdate
src/config.tswith your system name, package name, and agent instructionsShip stdio MCP to designers and engineers
Good when you need value fast and docs are still maturing.
Phase 2 — Live adapters (1–2 weeks)
Replace snapshot adapters with real integrations:
Adapter | Common sources |
| Storybook |
| Style Dictionary output, |
| MDX docs folder, public docs site (HTML → markdown like Primer) |
| CMS, static markdown, Notion export |
| Icon package manifest |
| Stylelint, custom JSX rules, a11y checks |
Phase 3 — Governance (ongoing)
CI job publishes refreshed snapshots on design-system releases
Add custom tools via
extraTools(e.g.review_jsx,suggest_token,migrate_component)Version MCP package alongside design-system semver
Adapter contract (minimal example)
import { createDesignSystemMcpServer } from '@ds-mcp/core';
export function createMyServer() {
return createDesignSystemMcpServer({
config: {
name: 'My Design System',
version: '1.0.0',
packageName: '@my-org/design-system',
instructions: 'Always use My DS components and tokens before custom UI.',
},
adapters: {
components: {
listComponents: () => [...],
getComponent: (name) => ({ id: 'button', name: 'Button' }),
},
tokens: {
findTokens: (query) => [...],
getGroupBundle: (group) => ({ id: group, name: group, tokens: [] }),
},
},
});
}Comparison with Primer MCP
Primer | This kit | |
Scope | Primer React only | Any design system |
Data | Primer packages + primer.style docs | Your adapters |
Tool names | Primer-specific set | Same standard surface |
Customization | Fork Primer repo | Config + adapters |
Best for | GitHub product UI | Enterprise / agency design systems |
Primer Brand also ships a separate @primer/brand-mcp with review/setup tools — your framework can add similar custom tools through extraTools.
Recommended repo layout for a team
your-design-system/
├── packages/
│ ├── tokens/
│ ├── react/
│ └── ds-mcp/ # MCP server package
│ ├── data/
│ │ └── catalog.snapshot.json
│ └── src/
│ ├── index.ts
│ ├── config.ts
│ ├── server.ts
│ └── adapters/
│ ├── components.storybook.ts
│ ├── tokens.style-dictionary.ts
│ └── docs.mdx.ts
└── .cursor/mcp.jsonRoadmap
CLI:
npm run create:ds-mcpgeneratorStorybook adapter template
Style Dictionary adapter template
Remote docs fetch adapter (cheerio + turndown, like Primer)
review_jsxtool for design-system complianceGitHub Action to refresh snapshots on release
Contributing
See CONTRIBUTING.md. Bug reports and pull requests are welcome.
License
MIT — see LICENSE.
References
This server cannot be deployed
Maintenance
Related MCP Connectors
Access and maintain design system docs, tokens, components, skills, and contexts across any project.
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
Let AI agents query data and act across all your business apps via MCP.
Pay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.
Related MCP Servers
- AlicenseAqualityCmaintenanceProvides AI agents with tools to access Material 3 design components, design tokens, icons, and accessibility guidelines across multiple frameworks.829 npm6MIT
- AlicenseNot gradedqualityDmaintenanceProvides resources, tools, and prompts for a Design System via MCP protocol, enabling component search, reading, and related component discovery.205 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to access design system tokens and component contracts through MCP, reducing token usage and ensuring consistency.29MIT
- AlicenseNot gradedqualityBmaintenanceAn 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