Ruixen MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listRegistryItemsC | Lists Ruixen UI registry items with optional filtering by kind, query, and limit. |
| getRegistryItemB | Gets detailed information for a single Ruixen UI registry item. |
| searchRegistryItemsB | Searches Ruixen UI registry items by keyword or use case. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: retrieving a single item, listing with filters, and searching. There is no overlap in purpose.
Tool names follow a verb_Noun pattern in camelCase, though getRegistryItem uses singular RegistryItem while the others use plural RegistryItems, a minor inconsistency.
Three tools cover the core retrieval and search operations for a registry. The count is reasonable, though slightly low if full CRUD were expected.
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.