Frontend Guru MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Frontend Guru MCP Convert this landing page screenshot into React code."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Frontend Guru MCP
Transform designs to Elevate 2.0 design system - MCP server + web interface
π― What This Does
Takes design inputs (URLs, screenshots, descriptions) and transforms them into production-ready React components that follow G2's Elevate 2.0 design system.
Two interfaces:
MCP Server - For Claude Code users (CLI + Desktop tab)
Web Interface - For everyone else (GUI, zero setup)
Related MCP server: stitch-pro-mcp
π Quick Start
For Claude Code Users (MCP Server)
1. Install dependencies:
npm install
npm run build2. Configure Claude Code/Desktop:
Add to your MCP config file:
Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json
Claude Code: ~/.claude/mcp_servers.json
{
"mcpServers": {
"frontend-guru": {
"command": "node",
"args": ["/Users/abedell/Developer/frontend-guru-mcp/dist/mcp/index.js"]
}
}
}3. Restart Claude
4. Use it:
/frontend-guru https://example.comClaude will ask you questions about format, then run the transformation.
For Web Interface Users
Coming soon - Will be deployed to: https://g2-frontend-guru.vercel.app
π Project Structure
src/
βββ core/ # Shared logic (used by both MCP and web)
β βββ agents/ # Agent prompts (orchestrator, analyzer, planner, etc.)
β βββ orchestrator/ # Transformation workflow
β βββ exports/ # Output format handlers
βββ mcp/ # MCP server (Claude Code)
βββ web/ # Web interface (Next.js) - TODOπ§ Development
Run MCP server in dev mode:
npm run dev:mcpBuild everything:
npm run buildπ Next Steps (TODO)
Complete web interface (Next.js app in
src/web/)Deploy web interface to Vercel
Implement actual agent workflow integration (currently returns mock data)
Add export handlers (ZIP, preview URL, clipboard)
Add progress tracking for long builds
Add build history/listing
π How It Works
User provides input (URL, screenshot, or description)
Analyzer agent identifies all sections in the design
Planner agent creates optimal build plan
Builder agent transforms design to React code (with design system rules)
Validator agent checks completeness and compliance
Refiner agent fixes any design system violations
Export in requested format (React, ZIP, preview, clipboard)
All agents follow the "transformation mindset" - adapting designs to match Elevate 2.0 standards, not just copying them.
π Documentation
Agents: See
src/core/agents/for all agent promptsDesign System Rules: See
src/core/agents/frontend-guardian.mdfor all 41 rulesOrchestrator: See
src/core/agents/orchestrator.mdfor workflow
π Troubleshooting
MCP server not showing up in Claude:
Check config file path is correct
Verify file has valid JSON (no trailing commas)
Restart Claude completely
Check logs: MCP server logs to stderr
Build fails:
Ensure all agents are present in
src/core/agents/Check that Node.js version is 18+ (
node --version)
π License
Private - G2 internal use only
Available Tools
1 toolfrontend_guru_transformA
Transform a design (URL, screenshot, or description) to Elevate 2.0 design system compliant React code
Inputs: source (required), format.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
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.
Maintenance
Related MCP Connectors
Live React design-system APIs, patterns, and code validation so AI agents build real UI, not slop.
UI design from prompts, screenshots, and URLs for AI coding agents and theme tokens.
Serves your design system and coding standards to coding agents, so they stop guessing.
Hosted Klaviyo MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables the generation and iterative refinement of React UI components from natural language descriptions or design images using Vercel's v0 API. It provides tools for design-to-code workflows and chat-based component development within Claude, Cursor, and other MCP environments.419MIT
- AlicenseAqualityDmaintenanceAn intelligent MCP server for Google Stitch that generates production-ready UI from text prompts, with auto-orchestration of design systems, WCAG accessibility, responsive breakpoints, and framework conversion (React, Vue, Svelte).1714 npm9MIT
- FlicenseBqualityDmaintenanceAutomated MCP server for the Insider Design System. Enables AI assistants to discover, understand, and generate code for over 60 Design System components with automated extraction from source code.14-
- FlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI agents to semantically retrieve premium UI components from Awwwards and adapt them into clean React + Tailwind code.1-