Skip to main content
Glama
uiverse-mcp

uiverse-mcp

by Fabi-SPL

uiverse-mcp

MCP server for Uiverse.io: browse, search, and use 3,800+ open-source UI components directly from Claude Code, Cursor, Codex, or any MCP-compatible AI agent.

No API key. No browser tab. Just ask for a "glass card" or "neon button" and get the full HTML + CSS back in your editor.

npm version License: Apache 2.0 MCP compatible


What it does

Uiverse.io has 3,800+ community-built UI components (buttons, cards, loaders, inputs, checkboxes, toggles, tooltips, etc.) with no official API. This server:

  1. Clones the uiverse-io/galaxy repo locally (~85 MB, one-time)

  2. Indexes all 3,800 components in memory (~2s startup, ~15 MB RAM)

  3. Exposes 7 MCP tools for browsing, searching, and fetching components

  4. Returns full HTML + CSS so your agent can drop components straight into your project


Related MCP server: aceternityui-mcp

Install

Add to your MCP config:

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

Option B: global install

npm install -g uiverse-mcp

Then add to MCP config:

{
  "mcpServers": {
    "uiverse": {
      "command": "uiverse-mcp"
    }
  }
}

Option C: clone and build

git clone https://github.com/Fabi-SPL/uiverse-mcp.git
cd uiverse-mcp
npm install
npm run build

Add to MCP config:

{
  "mcpServers": {
    "uiverse": {
      "command": "node",
      "args": ["/absolute/path/to/uiverse-mcp/dist/index.js"]
    }
  }
}

First run clones uiverse-io/galaxy into ~/.uiverse-mcp/cache (~30s, one-time). Cache is shared across all MCP clients.


Config locations

Client

Config file

Claude Code

~/.claude.json → mcpServers

Cursor

~/.cursor/mcp.json

Windsurf

~/.codeium/windsurf/mcp_config.json

Cline

VS Code settings → cline.mcpServers

Custom

Any MCP-compatible client


Tools

Tool

What it does

list_categories

All 11 categories with component counts, call this first

list_components

Browse a category, paginated, optional author filter

search_components

Fuzzy search by name, tag, or author

get_component

Fetch full HTML + CSS of a specific component

get_component_preview

Get the uiverse.io URL to preview a component in browser

refresh_cache

git pull the galaxy repo and rebuild the index

cache_status

Last sync time, commit SHA, total count per category


Categories (3,802 components)

Category

Count

Buttons

1,231

Cards

726

loaders

718

Toggle-switches

260

Inputs

226

Forms

180

Checkboxes

171

Patterns

103

Radio-buttons

102

Tooltips

62

Notifications

23


Example usage

In Claude Code:

User: I need a glassmorphism card for the pricing section.

Agent:
1. search_components({ query: "glass", category: "Cards", limit: 5 })
   → returns 5 matches with tags + preview URLs

2. User picks one

3. get_component({ category: "Cards", id: "elijahgummer_kind-pig-24" })
   → returns full HTML + CSS, ready to paste

Other queries that work well:

  • "neon glow button"

  • "neumorphic toggle"

  • "ripple loader"

  • "floating label input"

  • "gradient checkbox"


Configuration

Custom cache path

By default the galaxy repo is cached at ~/.uiverse-mcp/cache. Override with:

{
  "mcpServers": {
    "uiverse": {
      "command": "npx",
      "args": ["-y", "uiverse-mcp"],
      "env": {
        "UIVERSE_CACHE_PATH": "/your/custom/path"
      }
    }
  }
}

Architecture

src/
├── index.ts          MCP server entry (stdio transport)
├── cache.ts          Git clone / pull / metadata persistence
├── index-build.ts    Scan cache, build in-memory index
├── search.ts         Fuse.js fuzzy search
├── parse.ts          Extract author / name / tags / CSS from HTML
├── types.ts          Shared TypeScript types
└── refresh-cli.ts    Standalone CLI for cache refresh

Performance:

  • Startup: ~2s (index 3,800 files)

  • Search: < 30ms per query

  • Memory: ~15 MB RSS at idle

  • Disk: ~85 MB (shallow clone)


Data source & licensing

Components are sourced from uiverse-io/galaxy, MIT-licensed community contributions. This MCP server is Apache 2.0 licensed. When shipping a component, attribution to the original designer is appreciated (the author field is included in every response).


Contributing

Issues and PRs welcome at github.com/Fabi-SPL/uiverse-mcp.


License

Apache 2.0. See LICENSE and NOTICE.

Available Tools

7 tools
cache_statusA

Report cache metadata: last sync time, current commit SHA, total components indexed, per-category counts. Use to debug sync issues.

Inputs: no named parameters.

get_componentA

Fetch the full HTML + CSS of a specific component by category + id. Returns markup, CSS (or note if Tailwind-based), tags, author, preview URL. Use after browsing with list_components or search_components.

Inputs: id (required), category (required).

get_component_previewA

Return the public uiverse.io URL for visual preview of a component. Open this in a browser to see the component rendered with animations. Does NOT fetch HTML — use get_component for code.

Inputs: id (required), category (required).

list_categoriesA

List all Uiverse component categories with their component counts. Categories: Buttons, Cards, Checkboxes, Forms, Inputs, Notifications, Patterns, Radio-buttons, Toggle-switches, Tooltips, loaders. Call this first when you don't know what's available.

Inputs: no named parameters.

list_componentsA

List components in a specific category with pagination. Returns summaries only (id, author, name, tags, preview_url) — no HTML payload. Call get_component to fetch actual HTML/CSS for a specific component. Optional: filter by author.

Inputs: category (required), limit, author, offset.

refresh_cacheA

Pull the latest commits from the uiverse-io/galaxy repo and rebuild the in-memory index. Use when you suspect the cache is stale (last sync > 1 week). Returns commit SHA delta and new total count.

Inputs: no named parameters.

search_componentsA

Fuzzy search components by name, tags, or author. Returns top matches as summaries (no HTML). Use this when the user asks for a specific style like 'glowing button', 'glass card', 'ripple loader'. Optional category filter narrows the search.

Inputs: query (required), limit, category.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: listing categories, listing/searching components, fetching full component code, fetching preview URLs, and managing cache state. No overlap or ambiguity exists between tools.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_categories, list_components, search_components, get_component, get_component_preview, refresh_cache, cache_status). The naming is predictable and readable.

    Tool Count5/5

    Seven tools is well-scoped for a component library MCP server. The five component-related tools plus two cache-management tools cover the domain without bloat or thinness.

    Completeness5/5

    The tool surface covers the full workflow: discover categories, list components, search by style, fetch component code, and preview visually. Cache refresh and status tools handle maintenance edge cases. No obvious gaps in the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers