Skip to main content
Glama
Frontend Guru MCP

Frontend Guru MCP

by abedell-g2

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 build

2. 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.com

Claude 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:mcp

Build 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

  1. User provides input (URL, screenshot, or description)

  2. Analyzer agent identifies all sections in the design

  3. Planner agent creates optimal build plan

  4. Builder agent transforms design to React code (with design system rules)

  5. Validator agent checks completeness and compliance

  6. Refiner agent fixes any design system violations

  7. 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 prompts

  • Design System Rules: See src/core/agents/frontend-guardian.md for all 41 rules

  • Orchestrator: See src/core/agents/orchestrator.md for workflow


πŸ†˜ Troubleshooting

MCP server not showing up in Claude:

  1. Check config file path is correct

  2. Verify file has valid JSON (no trailing commas)

  3. Restart Claude completely

  4. 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 tool
frontend_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

    A3.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (frontend_guru_transform) with no inconsistency.

    Tool Count2/5

    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).

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      4
      19
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An 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).
      17
      14 npm
      9
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Automated 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
      -