search_components

Search and locate UI design system components by name, title, or category. Retrieve elements like modals, buttons, and forms with pagination for large result sets. Use direct queries or wildcards to streamline component discovery in Storybook systems.

Instructions

Search design system components by name, title, or category. Find UI components like modals, dialogs, popups, overlays, buttons, forms, cards, etc. Name is the component name only (e.g., "Modal", "Dialog"), title is the full story path (e.g., "Components/Overlays/Modal"), category is the grouping (e.g., "Components/Overlays"). Use "*" as query to list all components. Supports pagination for large result sets.

Input Schema

Name	Required	Description
`page`	No	Page number (1-based). Default is 1.
`pageSize`	No	Number of components per page (1-100). Default is 50.
`query`	Yes	The search query to match (e.g., "button", "form", "nav"). Use "*" to list all components. Case-insensitive partial matching.
`searchIn`	No	Where to search: "name" (component name only), "title" (full path), "category" (grouping), or "all" (search everywhere, default)

Input Schema (JSON Schema)

{
  "properties": {
    "page": {
      "description": "Page number (1-based). Default is 1.",
      "type": "number"
    },
    "pageSize": {
      "description": "Number of components per page (1-100). Default is 50.",
      "type": "number"
    },
    "query": {
      "description": "The search query to match (e.g., \"button\", \"form\", \"nav\"). Use \"*\" to list all components. Case-insensitive partial matching.",
      "type": "string"
    },
    "searchIn": {
      "description": "Where to search: \"name\" (component name only), \"title\" (full path), \"category\" (grouping), or \"all\" (search everywhere, default)",
      "enum": [
        "name",
        "title",
        "category",
        "all"
      ],
      "type": "string"
    }
  },
  "required": [
    "query"
  ],
  "type": "object"
}

MCP Design System Extractor