Server facts
feuse-mcp
Project
- Author
- Panzer-Jack
- Repository
- github.com/Panzer-Jack/feuse-mcp
- License
- Not specified
- Category
- Design & Creative
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 38
- Last commit
- Data as of
Tags
- d2c
- figma to code
- frontend
- mcp
- web mcp
Overview
Figma-to-frontend work in feuse-mcp combines explicit design styles with PNG reference images to generate code, adjusting the output to local configuration such as ESLint. Developers can target a Figma file or a particular node, extract SVG assets, and download SVG or PNG resources using image and icon node IDs. Color extraction reads Figma DSL and writes variables into a chosen structure, including UnoCSS, TailwindCSS, or a custom format. A separate comparison tool checks screenshots of implemented pages against Figma prototypes, providing similarity scores and analysis to support visual review.
Backend documentation drives another workflow: api-automation produces TypeScript interfaces, endpoint constants, mock data, and request functions from API descriptions. For coding-assistant context, initialize-project-standard examines the selected project's structure and creates global rules for Copilot and Cursor. The asset tools distinguish between analyzing a design to locate SVG resources and downloading resources identified by node IDs, with a local destination supplied for downloads. Together, these workflows serve frontend developers working across design handoff, API integration, and project-specific coding guidance.
feuse-mcp setup notes
- feuse-mcp records stdio only; confirm a network transport upstream before planning remote access.
- feuse-mcp has no recorded license; confirm reuse terms in its repository.