MCP.Market

UI Registry MCP server

by mrityunjay-tiwari·io.github.mrityunjay-tiwari/ui-registry-mcp·v0.7.1·5 stars
No reviews yet

Live access to 12 shadcn-style component libraries so agents compose UI from real components.

A88/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

5 stars62 downloads/wk

Reviews

Write one

Nobody has reviewed UI Registry yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

UI Registry tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_consistency

    Given a set of components (from get_component / search results), statically analyze their source for design clashes when mixed together: inconsistent border-radius scales, hardcoded colors vs theme tokens, missing dark-mode variants, and conflicting icon/animation libraries. Returns findings with concrete pointers so you can normalize the UI before shipping. Run this after assembling components fr

  • compare_components

    For a given intent (e.g. 'pricing table', 'date picker'), fetch the single best match from EACH library and return them side by side: dependencies, file count, lines of code, install command, and a source preview. Use this to choose the nicest implementation instead of taking the first search hit.

  • get_component

    Fetch the full, current source of one component from a specific library: file contents, npm dependencies, registry dependencies, and the exact install command. Use this after search_components. The returned source is real code you can drop into the project and edit freely. IMPORTANT: relay the returned 'attribution' line to the user so they know which library and source URL the component came from

  • list_components

    Browse the complete directory of every component across all libraries, each with its DIRECT URL (the registry JSON / shadcn install URL). Paginated — thousands of entries. Filter by registry and/or type, and page with offset/limit. Use this to enumerate what exists or to fetch a component's canonical source URL for attribution. Note: the directory includes premium/gated components too — some URLs

  • list_registries

    List the component libraries this server can pull from (id, name, homepage, license, and any notes such as premium/gated warnings). Call this first to see what is available. When a registry's notes mention premium/gated components, use verified:true in search_components to get only installable ones.

  • search_components

    Search all configured component libraries (or one) for components matching a natural-language query, e.g. 'pricing table', 'date picker', 'sidebar'. Synonym-aware: 'modal' also finds 'dialog', 'dropdown' finds 'select', etc. Returns a ranked, lightweight list (registry, name, type, title, description) — NOT the source. Pick the best match, then call get_component to fetch its real code. Set verifi

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan12 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 75 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How UI Registry compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
5
more than 83% of 28,688 servers
Downloads a week
62
more than 50% of 12,191 servers with a package

What its tools let an agent do: 6 read

Install UI Registry in Claude Code, Cursor or VS Code

Runs npx -y ui-registry-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ui-registry-mcp -- npx -y ui-registry-mcp
Add to Cursor

What the publisher says

From the UI Registry repository's README, as published. We do not edit it. Read it on GitHub

ui-registry-mcp

Coding agents are great at logic and not so good at taste. Ask one to build a pricing page and it'll hand-roll a flat, generic card from memory - when there are thousands of beautiful, open-source components sitting one fetch away that too built by people who are great UI/UX experts.

This is an MCP server that closes that gap. It plugs into Claude Code, Cursor, Windsurf, or any MCP client and lets the agent reach into 12 real component libraries — search them, pull the actual source, compare options, and check that everything looks like it belongs together — while you stay in your editor.

The idea is simple: the agent keeps the judgment (what to use, how to compose, what to tweak). The libraries keep the craft. This server is just the bridge.

Quick start

No cloning, no build. Point your MCP client at the published package:

{
  "mcpServers": {
    "ui-registry": {
      "command": "npx",
      "args": ["-y", "ui-registry-mcp"]
    }
  }
}

(In Claude Code you can also just run claude mcp add ui-registry -- npx -y ui-registry-mcp.)

Then ask for UI as:

"Build a cool pricing section - look across the libraries and pick the best component or tweaking them makes up a great pricing page."

"Add a data table and make sure it matches the card above."

Behind the scenes the agent searches, compares, pulls real code into your project, and does a quick design-consistency pass before it's done. It'll also tell you which library each piece came from, so you can credit and inspect the original.

What's inside

Twelve libraries, roughly 3,700 components, all fetched live — so you always get the current version, never a stale copy.

Everything the server hands you is openly licensed and free for commercial use — MIT across the board, except Vercel's AI Elements, which is Apache-2.0 (keep its license notice when you ship). A couple of libraries (ReUI, Aceternity) also list premium components in their catalog — those quietly fail to install. You don't have to think about it: ask for verified results and the server only returns things you can actually use. Still, check a library's own license before you ship.

Adding another library is one entry in src/registries.ts if it exposes a standard shadcn registry — nothing else changes.

The tools

Six tools, meant to be used roughly in this order:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

UI Registry: common questions

Is UI Registry MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the UI Registry safety report
How do I install UI Registry?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does UI Registry need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is UI Registry maintained?
The last commit was 114 days ago (2026-07-13). The latest release is v0.7.1.
How does UI Registry compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.