Ruixen MCP Server
Officialby ruixenui
README.md
# @ruixen/mcp
[](https://www.npmjs.com/package/@ruixen/mcp)
[](https://github.com/ruixenui/mcp.ruixen.com/actions/workflows/ci.yml)
Official [Model Context Protocol](https://modelcontextprotocol.io/) server for [Ruixen UI](https://ruixen.com/).
The server reads directly from the live [Ruixen registry](https://ruixen.com/registry.json), 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:
```json
{
"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.
## 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
```bash
npm install
npm run build # tsc + chmod
npm test # runs the live-registry smoke test (requires internet)
```
## License
[MIT](https://github.com/ruixenui/mcp.ruixen.com/blob/main/LICENSE.md)
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 issues