Generative-UI-MCP
Server 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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_ui_guidelinesA | Load detailed design guidelines for generating visual widgets. Call this before generating your first widget in a conversation. Available modules: interactive, chart, mockup, art, diagram. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| system-prompt | Compact system prompt with core widget rules. Inject into your system prompt for baseline compliance. |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possible confusion between tools.
With a single tool, naming is trivially consistent.
A server named 'Generative-UI-MCP' should have multiple tools for creating UI components, but only one tool for loading guidelines exists, which is insufficient.
The server lacks any tools for generating UI widgets, which is its stated purpose. The single tool only loads guidelines, leaving a major gap in functionality.