Remote MCP server for the Layro React and Tailwind component library, letting an assistant search components, read their props and source, and get install steps
What you can do
Search the Layro catalogue and list categories, with access level and version for each component and template found. Read a component's details: props, variants, npm dependencies, installed files, layout behaviour and related components. Retrieve full component source and imported files, or installation steps including the shadcn registry setup and CLI command. Check whether the caller may take a given component or template. Read the theme's colour tokens and restyling guidance, and get complete runnable recipe files that combine several components.
When to use it
Useful when building a React, Next.js or Tailwind interface and you want an assistant to find suitable Layro components, inspect their APIs and source, and wire them in with the correct install commands rather than guessing.
Requirements
A remote endpoint at layropro.com over streamable HTTP, added to the MCP client configuration. Search and component details need no account. Installing components requires an Authorization header carrying a Bearer CLI token from the Layro account page; a free account token covers free components, lifetime access covers Pro. Network access is required.
Before you install
The Authorization header carries a secret CLI token; keep it out of shared configs and repositories. Installing components depends on paid lifetime access for Pro items, and get_installation can produce a short-lived install token when a CLI token is present. Source and install output are meant to be written into your project, so review generated files before committing.
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.Uvxxsh%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.
Layro is a library of 112 production React UI components written in TypeScript and styled with Tailwind CSS (62 free).
Its remote MCP server gives Cursor, Claude Code, VS Code, Windsurf, Codex and other MCP clients access to the whole library.
Your agent can search the library, read each component's props and usage, and install the tested component with pinned packages.
Install
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
Search and component details work with no account. To install components, add the CLI token from https://layropro.com/account. A free account's token unlocks the 62 free components; lifetime access unlocks Pro:
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.
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
2
v1.0.2LatestOct 16, 2026
v1.0.1Oct 15, 2026
Score
90%
90% 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
License10 pts
Declare a license in the repository or the registry entry.