whata.design MCP · early access
The design MCP server.
36 tools that give your agent real websites to reference, measured sections to build from, and a reviewer that checks the result. For Claude Code, Cursor, Codex and any MCP client.
The design skill, MCP and book
Be first to use them. One email when they open, nothing else.
What your agent does with it.
Step 1
Finds references
recommend matches your brief to real sites, each with the reason it fits.
Step 2
Takes sections
get_library_section returns a measured section and its markup to adapt.
Step 3
Builds
get_base and get_recipe give audited parts and how to keep the chosen style accessible.
Step 4
Reviews
review_design loads the page at desktop and phone sizes and lists what fails.
Every tool.
The library
Real homepages to reference, searched by style, colour or similarity, each as facts an agent can build from.
Browse the librarylist_tagsEvery facet and term the library uses, with definitions.
search_sitesFind reference sites by style, layout, type, motion, text or audit state.
get_siteOne site's facts: tags, palette with roles, fonts, style record and what not to copy.
find_by_colorSites with a colour close to the one you give.
find_similarSites that share the most tags with a given site.
compareTwo sites side by side: shared and different tags, palette, fonts, theme.
get_design_briefA site's design written out: type scale, colours by role, spacing, radii, components, section map and images.
get_build_promptOne prompt for a builder: the task, a reference to study, the rules that matter and the recipes for the styles involved.
get_design_systemA site's tokens as DESIGN.md, JSON or CSS custom properties.
recommendMatches a written brief to styles and returns up to five reference sites, each with the reason it fits.
Sections and parts
Finished, measured pieces to build from instead of designing every part from scratch.
See the sectionsget_sectionsThe sections of any library site: type, position, height and what each holds.
get_sectionOne section of a library site: its desktop and mobile crops, scroll-video window and structure.
get_baseAudited page parts every build starts from: header with a real mobile menu, heroes, features, FAQ, form, footer.
get_backdropA full-bleed background drawn in code in the project's colours: aurora, field, contours.
list_library_sectionsThe pinned sections: what each is, its source, and what may change.
get_library_sectionOne section's measured spec, markup and the screenshot of its source.
Process and taste
A designer's process from need to launch, with the client's taste asked for, never assumed.
get_processThe design process: stages, steps, loops and the short tracks.
get_stepOne step's procedure, output template, gates and definition of done.
get_principlesNamed principles (Rams, Nielsen, Norman, inclusive design, Gestalt…) with how to apply and check them.
taste_intakeLibrary sites to show the client, spread across styles, and the question to ask.
propose_directionsSafe, stretch and wildcard directions from the client's picks, each anchored on real sites.
render_sheetSide-by-side sheets of design directions at desktop and phone sizes.
plan_graphicsA graphic for each section: a chart or diagram drawn from real content, type, an illustration or a real photograph.
record_tasteSaves what the client picked or said, in their own words.
get_taste_profileWhat this client leans toward and what is not for them, from everything they said.
taste_pairsA quick taste test: pairs of library sites for the client to choose between.
get_studioThe art-direction method: concepts, typography, layout, motion, by topic.
Rules and review
What separates a page that looks finished from one that is: testable rules, recipes, measurements and a reviewer.
Read the wikiget_guidelinesTestable rules for accessibility, usability, craft, copy, components and distinctiveness.
get_recipeHow to keep a stylish look (glass, brutalist, bento…) and still pass the rules.
get_trendsDated trend notes: what is rising, its risks and the overused version.
check_contrastWCAG contrast for colour pairs.
get_craftCraft numbers across the library: headline-to-body contrast, type steps, whitespace, motion.
compare_to_libraryMeasures a draft the same way and lists the gaps against the library.
get_movesRecurring moves of the best sites: what, why, how and the pitfalls.
get_critic_briefA fresh critic's brief and scoring rubric for a second opinion on a build.
review_designLoads a page at desktop and phone sizes, runs accessibility and usability checks, and returns what fails and how to fix it.
Pair it with the skill.
The skill is the design process the agent follows; the server is the library it calls on.
Questions.
What is a design MCP server?
An MCP server gives an AI agent tools it can call while it works. A design MCP server gives it design knowledge: here, real reference sites, measured sections, testable rules and a reviewer, so the agent designs from evidence instead of its own defaults.
How is it different from the Figma MCP server?
Figma's server turns the frames you already designed into code. This one helps when there is no Figma file: it gives the agent references, sections and rules to design with, and checks what it built.
Which clients does it work with?
Any client that speaks the Model Context Protocol: Claude Code, Claude Desktop, Cursor, Codex and others. It runs as a local server.
When can I use it?
It is in early access. Join the list for one email when it opens.
Do I need the skill too?
No, but they are made to work together: the skill is the process, the server is the library and the reviewer the process calls on.