@forgespace/ui-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_DSN | No | Sentry DSN for error reporting (uncaught exceptions and unhandled rejections). Optional. | |
| FIGMA_ACCESS_TOKEN | No | Token from Figma API settings. Only required for Figma-related tools. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scaffold_full_applicationB | Generate full project boilerplate with ML-composed pages for React, Next.js, Vue, Angular, Svelte, or HTML with Tailwind CSS and optional state management |
| generate_ui_componentB | 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. |
| generate_prototypeB | Create interactive HTML prototypes with screen flows, navigation, and transitions. Output is a standalone HTML file. |
| generate_design_imageB | Generate SVG or PNG mockup images of UI screens and components. Supports wireframe, mockup, and component preview modes. |
| fetch_design_inspirationC | Extract visual metadata (colors, typography, layout hints) from any URL to inform design decisions |
| figma_context_parserB | Read Figma file nodes, extract design tokens, and map them to Tailwind CSS utilities. Updates the shared design context. |
| figma_push_variablesA | Write design tokens back to Figma as Variables via the Figma REST API. Creates or updates variable collections. |
| analyze_design_referencesA | 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. |
| image_to_componentA | 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. |
| generate_page_templateB | 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. |
| refine_componentA | 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. |
| audit_accessibilityA | 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. |
| submit_feedbackB | Submit feedback on a previously generated UI component or page template. This helps UIForge learn your preferences and improve future generations. |
| analyze_design_image_for_trainingA | 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. |
| manage_trainingB | 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). |
| analyze_component_libraryA | Analyze component source code to detect which library is used, identify patterns, and get migration suggestions. |
| generate_component_libraryC | Generate components from shadcn, radix, headlessui, or material UI libraries. Supports themes, custom props, test/story generation, and framework-specific output. |
| get_available_componentsB | List all available components for a given component library (shadcn, radix, headlessui, material). |
| get_available_librariesA | List all available component libraries with their component counts and descriptions. |
| generate_from_template_packC | Generate a full multi-page application from a template pack |
| generate_api_routeB | Generate a production-ready API route with validation, authentication, and error handling based on best-practice backend patterns. |
| generate_backend_moduleB | Generate a complete backend feature module with routes, service layer, repository, types, and middleware following clean architecture patterns. |
| scaffold_backendA | 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. |
| generate_formA | 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. |
| payments_refundA | Request a refund for a payment. Validates payment_id, amount (positive integer minor units), optional reason and currency. Returns a structured confirmation (stub). |
| assess_legacy_codebaseA | 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. |
| generate_migration_planB | Generate a phased migration plan for a legacy codebase. Runs assessment, detects strategy, and produces a roadmap with quality gates (40% -> 60% -> 80%). |
| forge_scanA | 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. |
| forge_gateB | Run a quality gate check on a project. Returns pass/fail status, score, grade, and blocking violations. Configurable threshold and governance phase. |
| forge_diffA | Analyze quality delta between two git refs. Shows score change, new findings introduced, and resolved findings. Useful for PR quality checks. |
| forge_assessB | Run a full project health assessment across 5 categories (dependencies, architecture, security, quality, migration-readiness). Returns scores, grades, migration readiness, and prioritized findings. |
| forge_migrateB | 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. |
| setup_component_libraryC | Set up a complete project with a component library (shadcn, radix, headlessui, material) including config files, dependencies, and initial components. |
| validate_component_library_setupC | Validate that a component library is correctly configured in a project directory. |
| get_component_library_statusC | Get the current component library setup status for a project directory. |
| get_project_contextA | 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. |
| update_project_contextA | 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 — this completely replaces the existing context. |
| list_projectsA | Lists all projects registered in the centralized UIForge context store, with their slugs, titles, descriptions, and last-updated timestamps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| current-styles | Current design context with typography, colors, spacing, and other style tokens |
| forge-patterns-context | Core patterns and shared infrastructure for the Forge Space ecosystem |
| uiforge-webapp-context | Zero-cost web application for AI-driven UI generation |
| uiforge-mcp-context | AI-driven UI generation via Model Context Protocol |
| mcp-gateway-context | Central hub for MCP server management and routing |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Forge-Space/ui-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server