Docs / MCP Server
The catalog as an MCP server, so AI tools can browse and fetch real parts.
Models improvise interfaces when they cannot see real ones. The MCP server gives a connected AI tool the actual catalog — it can list what exists, search it, and fetch a part’s real files (HTML, CSS, JS) with its dependencies, then write them into your project as they are. It is the registry, served over the Model Context Protocol, from one zero-dependency Node file.
Download the server once, then point your MCP client at it. The configuration most clients accept:
curl -fsSL https://kata-ui.dev/mcp/kata-ui-mcp.mjs -o kata-ui-mcp.mjs
{ "mcpServers": { "kata-ui": { "command": "node", "args": ["/path/to/kata-ui-mcp.mjs"] } } }
Three, deliberately. list_components returns the catalog (optionally one type: parts, blocks, templates, themes). search_components finds candidates by name, title and description. get_component returns one item complete — every file’s full contents and the dependencies to bring along — which is the difference between a model describing a sidebar and installing this one.
The server is read-only: it serves the catalog and writes nothing, anywhere.
By default the server reads https://kata-ui.dev/registry.json at first use. Set KATA_BASE to a mirror, or pass --registry with a local file path, to serve a pinned or offline copy — the same mirror story as the CLI:
node kata-ui-mcp.mjs --registry ./registry.json
Introduction · Getting Started · CLI · Theming · Dark Mode · Accessibility · Installation · Plain HTML · Astro · Laravel · JavaScript · Guide: Building a Dashboard · Guide: Building a Settings Page · Guide: Building a Pricing Page · Guide: Sign-in & Account Pages · Why Vanilla · The Mold · Anatomy of a Part · Coming from Tailwind · FAQ · Registry · Forms · RTL · Changelog