Layro

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Search and install 112 production React, TypeScript and Tailwind CSS UI components from Layro.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Layro": {
      "url": "https://layropro.com/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (10)

• search_components read-only

  Find Layro React + Tailwind components by what they do. Returns the best matches first with slug, category, access (free or pro) and version. Start here, then call get_component for details.

  Parameters:

  • query (required) — string — What you need, in plain words: "animated dashboard card", "date range picker".
  • limit — integer — How many results. Default 8.
  • category — string — Only this category (name or slug from list_categories).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_component read-only

  Everything about one component except its source: when to use it, props, variants, npm dependencies, the files it installs, a typechecked usage example with real props, how it sizes and scrolls (layout), the components it pairs with and the recipes it appears in.

  Parameters:

  • slug (required) — string — A component slug, like "data-table".

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_component_code read-only

  The complete source for one component and every file it imports, ready to save at the paths given. Free components need a free Layro account's token; Pro components need the caller's Layro lifetime access. Install with the shadcn CLI instead when you can run commands (see get_installation).

  Parameters:

  • slug (required) — string — A component slug, like "data-table".
  • include_dependencies — boolean — Also return every file it imports (the theme, foundations, sibling components). Default true. Set false only if those are already in the project.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_installation read-only

  Installation for one or more components: the one-time @layro registry setup for components.json, the shadcn CLI command (always @layro/<slug>, never a bare URL), a ready-to-run agent command with a 15-minute install token when this connection carries a CLI token, the npm packages still missing (pass installed_packages from package.json), the files and where they go, and the theme setup.

  Parameters:

  • slugs (required) — array — One or more component slugs.
  • mode — string — Default "cli": the shadcn CLI install, packages and files. "manual" or "both" adds copy-by-hand steps, for when you cannot run the CLI.
  • package_manager — string — Default npm.
  • installed_packages — array — npm packages the project already has (from package.json), so they are not suggested again.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_categories read-only

  The categories in the Layro catalogue with the components in each, plus the library contract: stack, theme, access, install path, and the accessibility and responsive behaviour every component has.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• search_templates read-only

  Find complete Layro React / Next.js templates: what each is, its stack, a live preview and how it is licensed.

  Parameters:

  • limit — integer
  • query — string — What the template is for. Leave out to list all templates.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_template read-only

  One template's details and whether the caller may download it. Never returns the template's files.

  Parameters:

  • slug (required) — string — A template slug, like "settle".

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_access read-only

  Whether the caller can take a component or template, and why: free, subscriber, lifetime, purchased or unauthorized.

  Parameters:

  • slug (required) — string — A component or template slug.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_theme read-only

  The theme's colour tokens (light and dark values, and what each one colours), how to restyle Layro to a brand from your own CSS without editing components, the type scale, and the cn() config for it.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_recipe read-only

  Complete, runnable files that combine several Layro components the way they fit together: an AI chat app shell (Sidebar + Conversation History + AI Chat, with a phone drawer), a dashboard app and a billing page. Without a slug, lists the recipes. Every recipe typechecks against the components.

  Parameters:

  • slug — string — A recipe slug, like "ai-chat-app". Leave out to list the recipes.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.