AI & MCP

The shadcn CLI, and the MCP server built on it, only know the registries listed in your project's components.json. Add Velora with one command:

or add the entry yourself — {name} is filled in with the item you ask for:

{
  "registries": {
    "@velora": "https://velora.colorlib.com/r/{name}.json"
  }
}

Check it works — this lists every Velora item with “marquee” in it:

From then on, @velora/marquee works anywhere a component name does — in shadcn add, shadcn view and in your agent's requests.

The shadcn MCP server gives your editor's agent tools to browse, search and install items from every registry in components.json — Velora included. There is nothing Velora-specific to install. mcp init writes the config for your editor and adds shadcn to your dev dependencies.

{
  "mcpServers": {
    "shadcn": {
      "command": "npx",
      "args": ["shadcn@latest", "mcp"]
    }
  }
}

{
  "servers": {
    "shadcn": {
      "command": "npx",
      "args": ["shadcn@latest", "mcp"]
    }
  }
}

The CLI also supports --client codex and --client opencode; see the shadcn MCP docs for those and for troubleshooting.

Name the registry so the agent searches Velora rather than the default shadcn/ui one:

• Show me the components in the @velora registry
• Add @velora/marquee and use it for the logo strip on the home page
• Build a landing page from the hero, features and pricing blocks in @velora
• Find a Velora background for the hero and make it respect reduced motion

Installs go through the same CLI, so they bring the keyframes, brand tokens and npm dependencies each component needs.

No MCP? Every component page has a Copy prompt button under its title. It copies a self-contained brief you can paste into any chat or agent:

• the install command, and the file and dependencies it adds;
• a working usage example;
• every prop, with its type and default;
• what the component does when reduced motion is on;
• a link back to its docs page.

Try it on Marquee or Globe.

For agents that read the web rather than run tools, Velora publishes two plain-text files:

• /llms.txt

  An index of every component and block with a one-line description and its install command, plus each component's gzipped size and dependencies.

• /llms-full.txt

  The whole catalogue in one file: props, reduced-motion, keyboard and screen-reader notes, and a working example for every component. Hand it to an agent as context before it builds a page.

Both are generated from the same metadata as these docs, alongside the registry itself, so they list exactly what you can install.

The Open in v0 button on each component page sends its registry item to v0, so you can start a chat with the component already loaded and ask for changes.

One limit, from the shadcn docs: v0 doesn't load a registry item's css or cssVars. Components that ship their own keyframes or brand tokens may look static or unstyled there until you paste them in — the Manual install tab on each page lists that CSS.