dev.dryl/components · v3.12.0 · design
DRYL Components is healthy: it completed an MCP handshake in 1221 ms and exposes 4 tools.
Blazor UI library DRYL: find components, read their exact API and tokens, validate Razor markup.
Endpoint: https://components.dryl.dev/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 1221 ms |
| Last checked (UTC) | 2026-10-29T19:00:29.560Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-29T19:00:29.560Z | Healthy | 1221 |
search_components | Find 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_component | The 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="DrylButton.ButtonVar |
get_tokens | The 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 durations; DRYL follows the u |
validate_markup | Check 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; it does not compile |