MCP server

StyleKit MCP Server: Design Styles and Lint for Agents

StyleKit MCP gives an AI agent a library of named visual styles with design tokens, component recipes and a lint tool, so generated UI stops looking generic.

Run
npx -y --prefer-online stylekit-mcp@latest
View on GitHub

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

What is the StyleKit MCP?

StyleKit is an open-source MIT style library for AI-generated interfaces, and stylekit-mcp is its MCP server. It exposes search, design tokens, component recipes and a stylekit_lint_code tool for about 148 curated styles. The agent picks a named style, so output follows real tokens instead of drifting between prompts.

Asking an agent to make a page look good is not a spec, so results look alike. StyleKit turns a visual direction into a named style with tokens, hard constraints and examples the agent can follow.

The MCP server serves that library on demand. The agent searches for a style, reads its tokens and component recipes, and can lint generated code against the rules.

What you get

  • Named styles with design tokens and Tailwind constraints
  • Component recipes and copyable prompts
  • A lint tool that checks generated code against the chosen style
  • shadcn registry themes installed with a single command

Best for

  • Keeping an agent's UI output consistent across a project
  • Trying a distinct look quickly without writing tokens by hand
  • Teams already using shadcn and Tailwind

Who it is not for

The project says it does not promise production-ready interfaces, and integration still depends on your codebase. It also targets Tailwind and shadcn projects, so it fits other stacks less well.

Use it with UiChemy

Choose a style here, then pair it with the shadcn UI MCP for components, and use UiChemy to bring the finished design into WordPress.