Blazor UI library DRYL: find components, read their exact API and tokens, validate Razor markup.
Connect Remote server
claude mcp add --transport http components https://components.dryl.dev/mcp
{
"mcpServers": {
"components": {
"url": "https://components.dryl.dev/mcp"
}
}
}
{
"servers": {
"components": {
"type": "http",
"url": "https://components.dryl.dev/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://components.dryl.dev/mcp
Tools 4 found in our last check
search_componentsFind DRYL Blazor components (DRYL.Components and DRYL.Components.Agents) by name, title, category or purpose. Use this first when you need a component for a job; then call get_component for its exact API.
get_componentThe exact public API of one DRYL component: every parameter with type, default and description, the members of every enum it uses, its public methods and a canonical Razor example. DRYL variants are enums, never strings: write an enum value as qualifiedName.Member (e.g. Variant=…
get_tokensThe CSS custom properties DRYL styles itself with, grouped (colors, glass, accent, spacing, radius, motion, …), with the dark value and — where light mode differs — the light value. Reference these with var(--name) in your CSS instead of writing literal colors, sizes or duration…
validate_markupCheck a Razor snippet's <Dryl…> tags against DRYL's real API before you finish: unknown components, unknown parameters, and enum parameters given a string or a member that does not exist — each with a suggested fix. Call it on every DRYL markup you write or change. It scans tags…
Details
| Endpoint | https://components.dryl.dev/mcp (Streamable HTTP) |
| First published | 29 Oct 2026 |
| Last updated | 29 Oct 2026 |
| Registry name | dev.dryl/components |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
