Layro

io.github.LayroproPublished by GitHub account Layroprov1.3.0Updated Oct 29, 2026

React + Tailwind UI components and recipes your AI coding tool can search and install.

The publisher's own server: Layro

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Layro lets an AI coding assistant search, inspect and install production-ready React + Tailwind CSS v4 UI components, templates and recipes.

What you can do
  • Search the Layro catalogue for components by what they do, and browse categories with their components and library contract.
  • Read one component's details: props, variants, dependencies, installed files, layout behaviour, pairings and recipes.
  • Fetch a component's full source and every file it imports, or get shadcn CLI installation steps and registry setup.
  • Check whether the caller may take a given component or template, and list or inspect templates and their licensing.
  • Retrieve theme colour tokens and restyling guidance, and get complete runnable recipes such as a chat app shell, dashboard or billing page.
When to use it
Useful when building React or Next.js interfaces with Tailwind and you want the assistant to reuse existing components instead of writing them from scratch, or to assemble a whole screen from a ready-made recipe.
Requirements
A remote streamable HTTP endpoint at layropro.com; no local package. Searching works without credentials. Getting component code and installing needs an Authorization header carrying a Layro CLI token from a Layro account; free components need a free account, Pro components need lifetime access. The shadcn CLI and npm are needed for CLI-based installs.
Before you install
The connection carries a Layro CLI token in the Authorization header; the server may hand out a short-lived install token for CLI commands, which should not be written to files or pasted into chat. Installing writes component files into the project and adds npm dependencies. Access decisions are made server-side, and Pro components require paid lifetime access.

Installation

In SourceWeft

  1. Open Layro in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Layropro%2Flayro/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "layro": {
      "type": "http",
      "url": "https://layropro.com/api/mcp"
    }
  }
}

Tools

10

search_components

Search Layro components

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.

Parameterslimitqueryrequiredcategory

get_component

Get a Layro component

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.

Parametersslugrequired

get_component_code

Get a Layro component's code

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).

Parametersslugrequiredinclude_dependencies

get_installation

Install Layro components

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.

Parametersmodeslugsrequiredpackage_managerinstalled_packages

list_categories

List Layro categories

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.

Takes no parameters.

search_templates

Search Layro templates

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

Parameterslimitquery

get_template

Get a Layro template

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

Parametersslugrequired

check_access

Check Layro access

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

Parametersslugrequired

get_theme

Get the Layro theme

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.

Takes no parameters.

get_recipe

Get a Layro recipe

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.

Parametersslug

Version history

1
  1. v1.3.0LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Layro integrations