Frontend Guru 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| frontend_guru_transformA | Transform a design (URL, screenshot, or description) to Elevate 2.0 design system compliant React code |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools.
The single tool name follows a clear verb_noun pattern (frontend_guru_transform) with no inconsistency.
One tool is too few for a comprehensive design-to-code server. Typical scopes would require multiple tools for different aspects (e.g., validation, customization, export).
The single tool covers only the transformation step, lacking essential operations like validating outputs, adjusting parameters, or managing multiple designs. The surface is severely incomplete for the stated purpose.