UI MCP

@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

Framework & Library Support

Brand Identity Integration

All generation tools accept an optional brand_identity parameter — a JSON string from branding-mcp's generate_brand_identity tool. When provided, brand colors, typography, and spacing are injected into the design context.

Environment Variables

Distribution

• npm — published as @forgespace/ui-mcp
• MCP Registry metadata — repository includes server.json and mcpName metadata for registry submission
• Tag release automation — pushing v* runs npm publish with provenance, then publishes the same version to the MCP Registry via GitHub OIDC
• Weekly registry ops — .github/workflows/mcp-registry-status.yml refreshes one issue with npm and MCP Registry drift, visibility, and next actions
• GitHub — source, issues, releases, and Discussions live under Forge Space

Development

npm install && npm run build

npm test # 437 tests, 35 suites npm run validate # lint + format + typecheck + test

Community

• Documentation
• GitHub Discussions
• Issue Tracker

GitHub Workflow

This repository follows the shared Forge Space GitHub work-management baseline:

• Discussions for ideas, RFCs, Q&A, and announcements
• Issues for actionable delivery work
• Projects for roadmap visibility and cross-repo reporting

See Forge-Space/.github GOVERNANCE.md for the org-wide contract.

Scheduled monitoring runs that execute CodeQL require job-scoped security-events: write permission for SARIF upload.

The scheduled Security Monitoring workflow intentionally skips Codecov upload and relies on local coverage summary generation to reduce false alerting from third-party action download instability.

License

MIT