Design
kodza.dev
MCP server for searching and retrieving Kodza UI components, including their HTML/CSS/JS code, APIs, keyboard behavior, and dark-mode details.
ENDPOINT 1
https://kodza.dev/api/mcp
MCP server metadata
- Name
- kodza
- Version
- 0.1.0
Kodza is a free library of premium UI components and effects in plain HTML, CSS and vanilla JavaScript (no framework, no build step), made to be pasted into any site: a plain HTML page, WordPress, Shopify, or a React app. Use it when the user wants a polished UI element or effect (buttons, links, text effects, sliders and galleries, cards, navigation, scroll effects, preloaders and page transitions, forms, overlays, feedback, data display) without adding a framework: search_components to find one, then get_component for its exact code. Rules for the code you get: if you can run shell commands, download the CSS and JS files with the commands of the component's Files section (byte for byte what the Kodza site copies) instead of retyping them, and call get_component with inline: false to leave them out of the answer; only the HTML is yours to adapt and paste. Without a shell, paste the code as it is (HTML, CSS, JS), including the generated theme guard at the end of the CSS (the :not(#_) lines keep the site's own CSS from restyling buttons and fields); restyle through its --kz-* CSS variables, modifier classes and data- attributes rather than by editing its CSS; one copy of the JS per page serves every instance; for content inserted after page load, dispatch kodza:init on document with { detail: { root } } (and kodza:destroy before removing it). Components take the page's font; the Kodza look is Geist (Google Fonts). Each component comes with its dark-mode values (the "Dark mode" section): use them when the page has a dark theme. Building a Claude artifact (claude.ai)? Ask get_component with target "artifact": the artifact blocks images from other sites, among other limits.
Known tools 2
search_componentsFind Kodza UI components (plain HTML/CSS/vanilla JS) by what they do or look like, e.
Inferred read-onlyget_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 how to install it.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.kodza]
url = "https://kodza.dev/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"kodza": {
"type": "http",
"url": "https://kodza.dev/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: kodza
Remote MCP URL: https://kodza.dev/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"kodza": {
"url": "https://kodza.dev/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"kodza": {
"type": "http",
"url": "https://kodza.dev/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "kodza",
"transport": "streamable-http",
"url": "https://kodza.dev/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.