@ui-layouts/mcp

What it does

@ui-layouts/mcp is a local stdio server from the ui-layouts team that gives an assistant a way to browse the ui-layouts.com collection of UI components. It has four tools: one searches the component list by name, key, group, tags or link, one fetches a component's documentation page as plain text, raw HTML or just the main article, one reads the page's metadata (title, description, Open Graph and the site's own component-name fields), and one downloads a component's TSX code from the site's registry JSON.

It also ships two prompt templates, find_component and implement_component, that chain those tools into a search-and-recommend flow or a step-by-step integration guide for React, Next.js or Vite.

A detail the README leaves out: search_components does not query the website. It matches against a component list compiled into the package (src/registry.ts), returning 20 matches by default and up to 100 with limit, so components added to ui-layouts.com after a release only show up once a new package version lists them. The other three tools fetch live pages from https://ui-layouts.com with a 7-second timeout by default (1 to 20 seconds via timeoutMs) and cut their output to 8,000 characters for docs and 20,000 for source by default (up to 200,000 with maxChars).

What it needs

Node.js 20.10.0 or later to run it with npx, and outbound internet access to https://ui-layouts.com. No account, API key or settings are needed. An MCP client that starts stdio servers, such as Claude Desktop, Claude Code or Cursor.

Limits

Covers ui-layouts.com components only; it is not a general UI library search. Search runs over the component list bundled with the installed version, so newer components on the site are missing until the package is updated. get_source_code returns only the first file listed in a component's registry JSON, so components made of several files come back incomplete. Docs and source are truncated at maxChars (8,000 and 20,000 characters by default).

Who it suits

Suits developers who already build with, or are choosing components from, ui-layouts.com and want an assistant to find a fitting component and paste in its real TSX code instead of guessing. It runs locally, needs no sign-in and only reads public pages, so it is low-effort to add. It is no help for other component libraries or design systems; for those, use a server made for that library. Because search relies on a list fixed at release time, people who need the very newest components should check the site directly.