[Kodza: UI components your AI can fetch]
Kodza
UI components your AI can fetch. Plain HTML, CSS and JavaScript: no framework, no build step, no dependencies.
kodza.dev · Catalogue · Docs
Found a bug, or missing a component? kodza-dev/requests: issues for bugs, discussions for requests, with votes.
Just ask
Kodza is an MCP server too, at https://kodza.dev/api/mcp (Streamable HTTP). Free, no account, no API key. Plug it into your AI once:
Then ask in your own words: "Add the Kodza fill button to my hero." It gets the exact files in this repository, not its best guess, and where they go.
In your editor
Codex
VS Code (GitHub Copilot)
Cursor (~/.cursor/mcp.json)
Rather keep it on your machine? npx -y kodza-mcp runs the same server locally (kodza-mcp). Everything else in the docs.
What it does
Three slash commands too, for when you'd rather not write the request: build_page, replace_element and find_component (Claude Code: /mcp__kodza__build_page, VS Code: /mcp.kodza.build_page).
Read-only: it hands out code and never touches your project. It counts which components get fetched, and by which assistant; nothing you type is kept.
Six of them
Picked from the 208. Each picture runs its demo on kodza.dev, each name opens its files.
[Trapdoor Menu]
[Hero Showcase]
[Topographic Lines]
[Fill Button]
[Date Picker]
[Hover List Preview]
Trapdoor Menu · Hero Showcase · Topographic Lines · Fill Button · Date Picker · Hover List Preview
Or take the files
Each folder in components/ is one component: the HTML, the CSS and, when it needs one, the JS. Link the CSS, paste the HTML, load the JS. It lands in a bare HTML page, WordPress, Shopify or React, because it's just code.
Written like it's going live tomorrow. Because it probably is.
- The CSS only touches
kodza- classes. A generated theme guard keeps your site's CSS off the component.
- Settings are CSS variables (
--kz-…), variants are modifier classes or data- attributes.
- As many instances as you like on one page, one copy of the JS for all of them.
- Keyboard, visible focus and
prefers-reduced-motion, on every one.
kodza:init and kodza:destroy for content loaded later: AJAX themes, Swup, React.
The components
208 of them, and counting. Open a category: each name opens its folder, each demo runs on kodza.dev. All of them in motion: the catalogue.
Buttons · 15
Links · 10
Forms · 30
Navigation · 21
Overlays · 7
Feedback & loading · 6
Data display · 15
Cards · 5
Media · 6
Text effects · 9
Image effects · 9
Backgrounds & textures · 9
Scroll · 13
Cursor · 1
Preloaders & transitions · 7
SVG & Drawing · 6
Hero · 17
Header · 7
Footer · 6
Testimonials & logos · 6
Contact · 3
About this repository
It mirrors kodza.dev: when a component ships or changes there, it lands here. Every file is generated, none is edited by hand, so pull requests are not merged.
License
The Kodza License. Use the components in any project, personal or commercial, client work included, no attribution needed, and the house images that come with them too. Don't resell or redistribute them, and don't offer them through another catalogue, registry or MCP server.
Use it anywhere. Don't resell it.