Skip to main content
Glama
Ruixen MCP Server

Ruixen MCP Server

Official
by ruixenui

@ruixen/mcp

npm version CI

Official Model Context Protocol server for Ruixen UI.

The server reads directly from the live Ruixen registry, so the components your AI assistant can reach are always in sync with what's on ruixen.com.

Installation

Add to your IDE's MCP config:

{
  "mcpServers": {
    "ruixen-mcp": {
      "command": "npx",
      "args": ["-y", "@ruixen/mcp@latest"]
    }
  }
}

Works with any MCP-compatible client — Cursor, Claude Desktop, Windsurf, Cline, Roo-Cline, and VS Code (with an MCP extension). Each client stores this config in its own settings file; consult your client's docs for the exact location.

Related MCP server: aceternityui-mcp

Example Usage

Once configured, ask your AI assistant things like:

"Make a marquee of logos"

"Add a blur fade text animation"

"Add a grid background"

"Show me button components with spring animations"

The assistant calls the MCP tools below to discover components, pull their source, and hand you the exact npx shadcn@latest add … command to install each one into your project.

Available Tools

Tool

Description

listRegistryItems

List registry items with optional kind, query, limit, and offset filters. Good for broad browsing.

searchRegistryItems

Keyword search across names, titles, descriptions, and registry types, ranked by relevance. Good when you know roughly what you want.

getRegistryItem

Item detail for a specific component. Optionally includes source, examples, and relatedItems.

Development

npm install
npm run build   # tsc + chmod
npm test        # runs the live-registry smoke test (requires internet)

License

MIT

Available Tools

3 tools
getRegistryItemB

Gets detailed information for a single Ruixen UI registry item.

Inputs: name (required), includeSource, includeExamples, includeRelated.

listRegistryItemsC

Lists Ruixen UI registry items with optional filtering by kind, query, and limit.

Inputs: kind, query, limit, offset.

searchRegistryItemsB

Searches Ruixen UI registry items by keyword or use case.

Inputs: query (required), kind, limit, offset.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: retrieving a single item, listing with filters, and searching. There is no overlap in purpose.

    Naming Consistency4/5

    Tool names follow a verb_Noun pattern in camelCase, though getRegistryItem uses singular RegistryItem while the others use plural RegistryItems, a minor inconsistency.

    Tool Count4/5

    Three tools cover the core retrieval and search operations for a registry. The count is reasonable, though slightly low if full CRUD were expected.

    Completeness3/5

    The set covers reading, listing, and searching items but lacks create, update, or delete operations. This may be intentional for a read-only registry, but it's a notable gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides coding agents live access to shadcn-style component registries, enabling them to search, compare, and fetch real component source code for UI composition.
      5
      72 npm
      6
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to search, discover, and retrieve UI HUB components, source code, dependencies, templates, and animations via MCP.
      -