MCP.Market

UI MCP server

by Forge-Space·io.github.Forge-Space/ui-mcp·v0.25.0·2 stars

Forge Space MCP server for UI and backend generation via stdio transport.

C68/100grade C
What users say
No reviews yet
Be the first
Safety scan
C68/100

full report

Adoption
New

2 stars

Reviews

Write one

Nobody has reviewed UI yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

UI tools (38, 8 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • analyze_component_library

    Analyze component source code to detect which library is used, identify patterns, and get migration suggestions.

  • analyze_design_image_for_training

    Analyze a UI design image to extract patterns, styles, and components for ML training. Does NOT store images - only extracts structured design data (colors, typography, components, layout). Privacy-friendly and zero-cost.

  • analyze_design_references

    Analyze design references from URLs (browser automation + screenshots) and/or attached images. Extracts colors, typography, layout patterns, and UI components. When multiple references are provided, identifies common patterns across all sources to prioritize consistent design decisions for UI/UX generation.

  • assess_legacy_codebase

    Assess a legacy codebase for migration readiness. Analyzes dependencies, architecture, security, quality, and migration readiness. Returns health score (0-100), grade (A-F), migration strategy, and detailed findings.

  • audit_accessibility

    Audit a component for WCAG 2.1 accessibility violations. Checks color contrast hints, ARIA attributes, keyboard navigation, semantic HTML, form labels, focus management, and more. Returns issues with severity, suggestions, and WCAG criteria references.

  • fetch_design_inspiration

    Extract visual metadata (colors, typography, layout hints) from any URL to inform design decisions

  • figma_context_parser

    Read Figma file nodes, extract design tokens, and map them to Tailwind CSS utilities. Updates the shared design context.

  • figma_push_variableswrite action

    Write design tokens back to Figma as Variables via the Figma REST API. Creates or updates variable collections.

  • forge_assesswrite action

    Run a full project health assessment across 5 categories (dependencies, architecture, security, quality, migration-readiness). Returns scores, grades, migration readiness, and prioritized findings.

  • forge_diff

    Analyze quality delta between two git refs. Shows score change, new findings introduced, and resolved findings. Useful for PR quality checks.

  • forge_gatewrite action

    Run a quality gate check on a project. Returns pass/fail status, score, grade, and blocking violations. Configurable threshold and governance phase.

  • forge_migrate

    Generate a full migration plan for a legacy project. Combines health assessment with strategy recommendation, strangler boundaries, TypeScript migration plan, dependency risks, and a phased roadmap with quality gates.

  • forge_scan

    Scan a project for code quality issues using forge-ai-init governance rules (25 rules, 10 categories). Returns score, grade, findings by category, and hotspot files.

  • generate_api_route

    Generate a production-ready API route with validation, authentication, and error handling based on best-practice backend patterns.

  • generate_backend_module

    Generate a complete backend feature module with routes, service layer, repository, types, and middleware following clean architecture patterns.

  • generate_component_library

    Generate components from shadcn, radix, headlessui, or material UI libraries. Supports themes, custom props, test/story generation, and framework-specific output.

  • generate_design_image

    Generate SVG or PNG mockup images of UI screens and components. Supports wireframe, mockup, and component preview modes.

  • generate_form

    Generate production-ready forms with validation schemas, accessible markup, error handling, and multi-step support. Includes preset form types (login, signup, contact, checkout) or fully custom field definitions.

  • generate_from_template_pack

    Generate a full multi-page application from a template pack

  • generate_migration_plan

    Generate a phased migration plan for a legacy codebase. Runs assessment, detects strategy, and produces a roadmap with quality gates (40% -> 60% -> 80%).

  • generate_page_template

    Generate pre-built page templates for common UI patterns: landing pages, dashboards, auth flows, pricing, settings, CRUD tables, blog listings, onboarding wizards, error pages, and ecommerce storefronts (PLP, PDP, cart, checkout). Supports all frameworks and component libraries.

  • generate_prototypewrite action

    Create interactive HTML prototypes with screen flows, navigation, and transitions. Output is a standalone HTML file.

  • generate_ui_componentwrite action

    Create or iterate UI components with style audit and design context awareness. Supports React, Next.js, Vue, Angular, Svelte, and HTML. Component library integration available: shadcn/ui, Radix UI, Headless UI, PrimeVue, Material UI.

  • get_available_components

    List all available components for a given component library (shadcn, radix, headlessui, material).

  • get_available_libraries

    List all available component libraries with their component counts and descriptions.

  • get_component_library_status

    Get the current component library setup status for a project directory.

  • get_project_context

    Returns the full context document for a UIForge project from the centralized store. This is the absolute source of truth for project architecture, status, requirements, and roadmap. Pass the project slug (e.g. "forge-patterns"). Use list_projects to discover available projects.

  • image_to_component

    Convert a screenshot, mockup, or wireframe image into framework-specific component code. Supports React, Next.js, Vue, Angular, Svelte, and HTML. Optionally uses shadcn/ui, Radix, Headless UI, PrimeVue, or Material UI.

  • list_projects

    Lists all projects registered in the centralized UIForge context store, with their slugs, titles, descriptions, and last-updated timestamps.

  • manage_training

    Manage ML training jobs for the UIForge sidecar model. Actions: check_readiness (verify training prerequisites), start_training (begin LoRA fine-tuning), get_status (check job progress), cancel_training (stop running job), list_adapters (show available adapters), get_summary (get training statistics).

  • payments_refundwrite action

    Request a refund for a payment. Validates payment_id, amount (positive integer minor units), optional reason and currency. Returns a structured confirmation (stub).

  • refine_component

    Iteratively improve an existing component based on natural language feedback. Apply accessibility fixes, dark mode, responsive improvements, component library upgrades, and design context alignment. Supports all frameworks.

  • scaffold_backend

    Generate a complete production-ready backend project scaffold. Supports Express and Next.js with configurable features: auth (JWT/OAuth/Session), database (Prisma/Drizzle), API docs (Swagger), monitoring (Sentry), caching (Redis), and more. Includes TypeScript, testing, and CI/CD setup.

  • scaffold_full_application

    Generate full project boilerplate with ML-composed pages for React, Next.js, Vue, Angular, Svelte, or HTML with Tailwind CSS and optional state management

  • setup_component_library

    Set up a complete project with a component library (shadcn, radix, headlessui, material) including config files, dependencies, and initial components.

  • submit_feedbackwrite action

    Submit feedback on a previously generated UI component or page template. This helps UIForge learn your preferences and improve future generations.

  • update_project_contextwrite action

    Writes or overwrites the context document for a UIForge project in the centralized store. Use this to keep the source of truth up-to-date after architectural decisions, status changes, roadmap updates, or any significant project change. Provide the full markdown content \u2014 this completely replaces the existing context.

  • validate_component_library_setup

    Validate that a component library is correctly configured in a project directory.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

1 high
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancerepository archived0/15
  • Maintainer identityregistry namespace matches repository owner7/10

Findings (1)

  • highRepository is archivedmaint.archived
Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How UI compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
68/100
higher than 30% of 48,255 servers
Tools
38
the typical server has 7
Tools that change things
21%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 75% of 28,688 servers

What its tools let an agent do: 21 read · 10 create · 7 change

Install UI in Claude Code, Cursor or VS Code

Runs npx -y @forgespace/ui-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ui-mcp -- npx -y @forgespace/ui-mcp
Add to Cursor

What the publisher says

From the UI repository's README, as published. We do not edit it. Read it on GitHub

@forgespace/ui-mcp AI-driven UI and backend code generation via Model Context Protocol. 22 tools, 5 frameworks, brand-aware, npm-published, and MCP Registry-ready.

Part of the Forge Space ecosystem.

Architecture

@forgespace/ui-mcp is a thin protocol adapter. All AI/generation logic lives in @forgespace/siza-gen:

@forgespace/ui-mcp (~355 KB)       @forgespace/siza-gen (~1.8 MB)
├── src/index.ts (MCP server)      ├── ml/        (embeddings, quality, training)
├── tools/     (22 tool defs)      ├── generators/ (react, vue, angular, svelte, html)
├── services/  (figma, analysis)   ├── registry/   (502 snippets, compositions, packs)
├── resources/ (MCP resources)     ├── feedback/   (self-learning, pattern promotion)
└── lib/       (browser, image)    └── quality/    (anti-generic rules, diversity)

Quick Start

# NPX (instant)
npx -y @forgespace/ui-mcp@latest

# Global install
npm install -g @forgespace/ui-mcp && forgespace-ui-mcp

# Docker
docker build -t forgespace-ui-mcp . && docker run --rm -i forgespace-ui-mcp

IDE Integration

Add to your MCP configuration (Claude Code, Windsurf, Cursor, VS Code):

{
  "mcpServers": {
    "forgespace-ui-mcp": {
      "command": "npx",
      "args": ["-y", "@forgespace/ui-mcp@latest"],
      "env": {
        "FIGMA_ACCESS_TOKEN": "your_token_here"
      }
    }
  }
}

Tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

UI: common questions

Is UI MCP server safe?
With care: it is graded C, so read the findings first (68/100). Read the UI safety report
How do I install UI?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does UI need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is UI maintained?
The last commit was 198 days ago (2026-04-20). The latest release is v0.25.0.
How does UI compare with other MCP servers?
safety score 68/100 (higher than 30% of 48,255 servers); tools 38 (the typical server has 7); tools that change things 21% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.