Skip to main content
Glama
Sign In
uikit-registry

uikit-registry

by captainy7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

uikit-registry 🎨

Registry 13 UI library + MCP server untuk AI.
Cari, bandingin, dan dapetin detail komponen UI dari 13 library populer — langsung dari AI agent (OpenCode, Claude, dll).

npm run mcp-server   →   search_component + get_component + compare_components

✨ Fitur

Fitur

Tools MCP

🔍 Cari komponen di semua library

search_component(query)

📦 Ambil detail komponen + source code + props

get_component(library, component)

⚖️ Bandingin komponen antar library

compare_components(component, libraries?)

13 library UI

shadcn, MUI, Chakra, Antd, Mantine, NextUI, Radix, DaisyUI, PrimeReact, Neobrutalism, Aceternity, Magic UI, Origin UI

Props real dari TypeScript .d.ts

MUI ✅, shadcn ✅

0 runtime dependencies

Node.js aja

Related MCP server: MCP Server Starter Template

🚀 Quick Start

1. Clone & Setup

git clone https://github.com/captainy7/uikit-registry.git
cd uikit-registry
npm install
npm run build

2. Jalankan MCP Server

npm run mcp-server

Output:

🔌 uikit-registry MCP server v2 (data: ./data)
   Tools: search_component, get_component, compare_components
   Libraries: 13

3. Daftarin di OpenCode / Claude

Edit ~/.config/opencode/opencode.json:

{
  "mcpServers": {
    "uikit-registry": {
      "command": "node",
      "args": ["/home/satria/Development/uikit-registry/dist/mcp-server.js"],
      "env": {
        "UIKIT_DATA_DIR": "/home/satria/Development/uikit-registry/data"
      }
    }
  }
}

Restart OpenCode, langsung bisa pake tools uikit-registry.

📦 Data

Library

Komponen

Props

Version

shadcn/ui

358

✅ source code + CVA props

—

MUI

131

✅ 14+ props dari .d.ts

v9.1.2

Chakra UI

115

—

v3.36.0

Ant Design

80

—

v6.4.5

Mantine

114

—

v9.4.0

NextUI / Heroui

85

—

v3.2.1

Radix UI

59

—

—

DaisyUI

46

—

v5.5.23

PrimeReact

124

—

—

Aceternity UI

88

—

—

Magic UI

47

—

—

Origin UI

76

—

—

Neobrutalism

16

—

—

Total

1339

—

—

🛠️ Usage Examples (via AI Agent)

Cari komponen:

search_component("button")
→ 11 library punya button

Lihat detail:

get_component("shadcn", "button")
→ import, 4 props (variant, size, className, asChild), source code

Bandingkan:

compare_components("dialog", "shadcn,mui")
→ shadcn: 0 props
→ mui: 20 props (transition, paper, container, backdrop, ...)

📋 Scraping Manual

# Scrape semua library
npm run scrape

# Scrape satu library aja
tsx src/scraper.ts --lib shadcn

# Output: data/{library}/{component}.json
# Index: data/index.json

Scraping otomatis tiap minggu via GitHub Actions (.github/workflows/scrape.yml).

🧪 Tests

npm test
# 125 tests, 0 fail
npm run typecheck
# TypeScript strict, 0 errors

🏗️ Arsitektur

src/
├── scrapers/       # 13 scraper, masing-masing file sendiri
├── mcp/            # MCP server + tools
├── data/           # Data access layer (ComponentStore)
└── shared/         # Types, constants, utils

  • TypeScript strict — semua tipe aman

  • Zero runtime deps — cuma node.js

  • 100% local — gak perlu GitHub API / internet

  • Parallel scraper — 13 library selesai ~1 menit

📄 License

MIT

Available Tools

3 tools
compare_componentsA

Bandingkan komponen yang sama dari dua atau lebih library. Melihat perbedaan props, import path, dan source code.

Inputs: component (required), libraries.

get_componentA

Ambil detail komponen dari library tertentu. Dapat source code (shadcn) atau props + contoh (MUI, Chakra, dll).

Inputs: library (required), component (required).

search_componentA

Cari komponen UI di semua library. Return daftar library yg punya komponen itu.

Inputs: query (required), library.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: search finds components across libraries, get retrieves details from a specific library, compare contrasts same component across libraries. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (compare_components, get_component, search_component) with snake_case.

    Tool Count5/5

    Three tools is appropriate for a focused UI component registry, covering search, retrieval, and comparison without unnecessary bloat.

    Completeness4/5

    Covers core operations well, but a tool to list all libraries or components directly might be missing; however, search can approximate this.

    Resources

    Related MCP Connectors

    Related MCP Servers