Skip to content
GitHub MCP RegistryListed

Kodza

Part ofKodzalisted on 3 directories

Free premium UI components in plain HTML, CSS and vanilla JS, for AI coding assistants.

First seen 31 Oct 2026. Evidence as of 16 Nov 2026.

2
Tools
From an anonymous probe
1
Source listings
Each with its own history
9
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
get_componentThe full code of one Kodza component (HTML, CSS and, when it has one, vanilla JS), its API (CSS variables with defaults, modifier classes, data attributes, events), what each key does when it takes the keyboard, its dark-mode values and its install notes. Its CSS and JS are also available as files at the URLs listed in its Files section; with inline: false, the answer leaves them out of the Code section. target narrows the install notes to one stack.Read-only
search_componentsFind Kodza UI components (plain HTML/CSS/vanilla JS) by what they do or look like, e.g. "button fill hover", "image slider", "sticky header", "date picker". An empty query lists a whole category. Returns the slugs get_component takes.Read-only

Change history

  1. server instructions changed (+"JS" +"build) for" +"search_components finds them by what they do or look like; get_component returns one: its HTML, CSS and JS exactly as kodza.dev copies them, also as files, its API, keys, dark-mode values and install notes per target. Guide: https://kodza.dev/docs/. A site makes them its own, no edit to their CSS or JS: - Shared variables on :root apply to every component. Colours: --kz-color-ink (text, icons, rules, shades), --kz-color-paper (cards, fields, panels, menus), --kz-color-page (full-width backgrounds); optional: --kz-color-accent, --kz-color-on-accent, --kz-color-error. Type: --kz-font-display, --kz-font-label, --kz-font-mono. Corners: --kz-radius-scale, --kz-radius-pill. Fields: --kz-field-width. Page: --kz-page-width, --kz-page-gutter (one column for header, sections, footer and your containers). Pace: --kz-motion-scale (0: no motion). A site's palette is these, not each component's own colour variables. Unset, nothing changes; get_component names those each reads. - The CSS ends with a theme guard (the :not(#_) lines), which keeps display and position on the root: a wrapper element around it moves or hides it. A page rule on a component's class loses to the guard on what it holds unless its selector ends with :not(#_); a rule on an inner element (kodza-x__y) is the last resort. - Texts a script writes (a placeholder, a "Done" button) are data-text-* attributes on the root, under API as Texts with English defaults: a site in another language sets each one and translates the HTML. - A date or time field has none typed in its markup, the demo's included: its min, max, value and slots are computed by the page's script at load. - Components never style html: a one-page with a sticky header sets html { scroll-padding-top: <header height> }, and html { scroll-behavior: smooth } inside @media (prefers-reduced-motion: no-preference). In more detail:")
  2. server instructions changed (+"The theme guard also holds display and position on a component's root, and the margin of a root that is a button: a page rule on the root does not move, hide or space it, while the same rule on a wrapper element around the component does. Other margins and float on a root stay the page's." +"sticky component sticks only inside its parent, so a wrapper of its own height keeps it from sticking. Each component is checked for horizontal overflow on a 375 px wide screen, in its own demo; a page built from components is not, so an overflow there, such as a component that a page rule failed to hide, appears only once that page is open at that width. A" +"Components never style html, so how the page itself scrolls stays the page's: a one-page whose links lead to its sections glides there and stops below a sticky header only with html { scroll-padding-top: <the header's height once scrolled> } in the page's CSS, and html { scroll-behavior: smooth } inside @media (prefers-reduced-motion: no-preference); the install notes of each sticky header give its height.")
  3. search_components: description changed (+"An empty" +"lists" +"the")
  4. get_component: input schema changed
  5. get_component: description changed (+"its" +"notes." +"available")
  6. server instructions changed (+"app or" +"Claude artifact. It covers buttons," +"feedback and")
  7. server instructions changed (+"the small labels (meta, captions, counters, hints under" +"field, footer links, header bar links, button and tab labels) follow --kz-font-label with --kz-font-label-size (one size for all of them), --kz-font-label-weight, --kz-font-label-tracking, --kz-font-label-case and --kz-font-label-leading; a" +"Motion follows the site too: --kz-motion-scale on :root multiplies every duration of every component, CSS and scripts (0.5 twice as fast, 2 twice as slow, 0 no motion at all, loops stopped, like reduced motion); set on one component, it paces that one only.")
  8. server instructions changed (+"A site with its own type sets it once on :root for every component, never by editing their CSS: --kz-font-display (headings, big numbers, wordmarks) with --kz-font-display-weight, --kz-font-display-scale (a multiplier on their sizes), --kz-font-display-tracking and --kz-font-display-case (uppercase…), and --kz-font-mono (code, labels, counters); a heading that needs another size takes its own --kz-font-display-scale on its element; unset, nothing changes, and get_component names the ones each component reads. Corners work the same way: --kz-radius-scale on :root multiplies every corner (0 square, 0.5 softer, 1 Kodza) and --kz-radius-pill sets the pills (0 squares them). Form fields share one width: --kz-field-width on a form (or :root) sizes every Kodza field in it (100% fills the column).")
  9. Listed (GitHub registry)
Source listings
SourceListingFirst seenLast seenVersions
GitHub MCP Registrydev.kodza/kodza31 Oct 202616 Nov 20261