---
name: index
description: Find design resources for the current project in Index, a reviewed catalog of component libraries, shadcn registries, templates, fonts, icons, motion, and inspiration, with install commands and licenses. Use it when the user asks for a UI component, a library, a template, a font, an icon set, or design references.
---

# Index

Index is a reviewed catalog of design resources: component libraries, shadcn registries, templates, fonts, icons, motion, inspiration galleries, studios, and design tools for agents.

## Connect

- MCP server: https://index-mcp.chele.bi/mcp (Streamable HTTP, no key). Tools: search, fetch, component_guide.
- Without MCP: GET https://index-mcp.chele.bi/search?q=date+range+picker&framework=react returns the same JSON as the search tool.
- Static files: https://index.chele.bi/api/r/<id>.json for one record, and /api/components/<component>.json for one component.

## Search rules

1. Read the project stack first (package.json, the Tailwind config) and pass it as filters.
2. Ask for one need per search. Describe the need, for example "date range picker with presets", instead of a guessed product name.
3. Use component or surface when the need is a UI part or a page type. For a look, put a style in the query, for example "brutalist portfolio" or "dark glow homepage".
4. Treat match "weak" or "none" as a real answer. Widen the filters, or call component_guide and build the part yourself.
5. Call fetch on your pick and check its license before you install it.

## Read the results

- match is strong, weak, or none. With none, say that Index has nothing that fits. Do not force a pick.
- why lists what each result matched: a component, a filter value, a style, or similar meaning.
- install is the command to run. items lists single registry items with their own install command.
- Filters are hard limits. When nothing passes, the search drops one and lists it in relaxed.