Web Design MCP
The Model Context Protocol lets AI agents call external tools mid-build. A web design MCP is a server that gives those agents structured design knowledge: real typography systems, colour palettes, layout patterns, and component guidance, so they stop guessing and start building with taste.
The problem
AI builders default to generic.
Without a design reference, every AI-generated site converges on the same patterns: centred hero with a gradient, Inter or system fonts, a blue primary, stock spacing. The output is functional but forgettable.
A web design MCP changes the equation. Instead of generating from training averages, your agent queries a structured library of real, deeply-analysed websites and builds from evidence.
Palate
The web design MCP with real depth.
Palate analyses 268 production websites across 916 inner pages. Not just homepages: pricing pages, documentation, feature tours, about pages. Each reference is broken into structured facets your agent can reason over.
Facets
Layout, typography, colour, motion, component patterns, and copy tone. Structured data, not screenshots.
The taste layer
Do/don't rules and component prompts for every reference. Your agent gets explicit craft guidance.
Design tokens
Extracted colours, type scales, spacing systems, and radius patterns. Ready to apply or blend.
The difference
Without vs with a web design MCP.
Without
- Centred H1, subtitle, button (the stock hero)
- Inter or system font, blue primary
- Generic spacing, no rhythm
- Every site looks like every other site
With Palate
- Layout grounded in a real reference (off-centre, editorial, bespoke)
- Distinctive type pairing from a proven system
- Extracted spacing and radius tokens
- Craft guidance your agent follows
Install
One line. Any MCP-compatible agent.
Add Palate to Claude Code, Cursor, or Windsurf and every build from that point has the full library behind it.
Claude Code
claude mcp add palate \
--url https://mcp.palatemcp.com \
--header "Authorization: Bearer plt_live_..."