Categories › Software Development › Frontend, UI components & design-to-code
Blazor UI library DRYL: find components, read their exact API and tokens, validate Razor markup.
Remote server: your requests and data go to components.dryl.dev. Claude Code: claude mcp add --transport http dryl-components https://components.dryl.dev/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_components — Find DRYL Blazor components (DRYL.Components and DRYL.Components.Agents) by name, title, category or purpose. Use this first when you need aget_component — The exact public API of one DRYL component: every parameter with type, default and description, the members of every enum it uses, its publiget_tokens — The CSS custom properties DRYL styles itself with, grouped (colors, glass, accent, spacing, radius, motion, …), with the dark value and — whvalidate_markup — Check a Razor snippet's <Dryl…> tags against DRYL's real API before you finish: unknown components, unknown parameters, and enum parameters Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.