Feuse (Figma Design-to-Code)

Feuse (Figma Design-to-Code)

panzer-jack

Converts Figma designs to code by extracting design tokens, downloading assets, and generating CSS variables for frameworks like TailwindCSS and UnoCSS.

Automates Figma design-to-code workflows by extracting design data, downloading SVG assets, analyzing color variables, and generating API models with design token conversion for CSS frameworks like UnoCSS and TailwindCSS.

39373 views11Local (stdio)

What it does

  • Extract design tokens from Figma files
  • Download SVG and PNG assets automatically
  • Generate CSS variables for TailwindCSS/UnoCSS
  • Convert Figma color variables to design tokens
  • Compare generated code with original designs
  • Generate TypeScript interfaces from API docs

Best for

Frontend developers converting Figma designs to codeDesign system teams maintaining design tokensWeb developers automating asset extraction workflows
Built-in Figma integrationMultiple CSS framework supportAutomated design-to-code validation

About Feuse (Figma Design-to-Code)

Feuse (Figma Design-to-Code) is a community-built MCP server published by panzer-jack that provides AI assistants with tools and capabilities via the Model Context Protocol. Automate your figma to code workflow. Convert Figma designs to HTML, extract SVGs, analyze color, and generate CSS with It is categorized under developer tools.

How to install

You can install Feuse (Figma Design-to-Code) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

Feuse (Figma Design-to-Code) is released under the MPL-2.0 license.

feuse-mcp

Frontend Useful MCP (Model Context Protocol) Tools - Essential utilities for web developers to automate API integration, Figma design-to-code conversion, and development workflow optimization.

license license

English | 中文

📖 Documentation

feuse-mcp Official Documentation

✨ Features

  • 🎨 Figma Integration: Built-in integration with Figma-Context-MCP for seamless Figma design-to-code conversion and automatic asset extraction
  • 📝 API Automation: Generate TypeScript interface types, API URL constants, mock data, and request functions from API documentation
  • 🖼️ Asset Management: Download SVG and PNG images from Figma files with organized file structure
  • 🎯 Similarity Comparison: Compare generated code pages with original Figma prototypes for accuracy validation
  • 🛠️ Project Standards: Generate global specification guidance files for Copilot & Cursor based on current project architecture
  • 🔧 Color Variables: Extract and convert Figma color variables to CSS/design tokens in specified standards (UnoCSS, TailwindCSS, or custom structures)

🔧 Available Toolset (Continuously Updated)

Tool NameCategoryDescriptionInput ParametersNotes
Figma-To-CodeFigma IntegrationGenerate frontend code based on Figma styling info with PNG assistancefileKey, nodeId(optional)Auto-adapts to local configs (ESLint etc), supports responsive layouts
extract-svg-assetsAsset AnalysisAnalyze Figma DSL structure and auto-extract SVG resourcesfileKey, nodeId(optional)Intelligent Figma file analysis, batch extraction of SVG icons/vectors
extract-color-varsDesign TokensExtract color variables from Figma DSL to CSS framework configsfileKey, nodeId(optional)Supports UnoCSS, TailwindCSS, or custom file format output
similarity-figmaQuality ControlCompare Figma prototypes with project page screenshotsurl, fileKey, nodeId(optional)Visual comparison with intelligent similarity scoring and detailed analysis
api-automationDevelopment ToolsParse backend API docs and generate types, constants, mock dataapiDocsSupports multiple API doc formats, generates complete frontend API toolkit
initialize-project-standardProject ManagementAnalyze project structure and generate Copilot/Cursor global rulesNo parametersAuto-generates intelligent coding assistant project context and standards
Download-Figma-ImagesAsset ManagementBatch download SVG and PNG image resources from Figma by node IDfileKey, nodes[], localPathSupports imageRef handling, auto-creates directory structure (low-level tool for other MCPs)
download-svg-assetsAsset ManagementDownload SVG vector resources from Figma by image/icon node IDfileKey, nodes[], localPathSVG format only, supports complex node structures (low-level tool for other MCPs)

🚀 Quick Start

Configuration

Add to your MCP client configuration:

Get your Figma API key from Figma Developer Settings.

{
  "feuse-mcp": {
    "command": "npx",
    "args": ["feuse-mcp@latest"],
    "env": {
      "FIGMA_API_KEY": "YOUR_FIGMA_API_KEY"
    }
  }
}

🔧 For Code Contributors

Setup

# Clone the repository
git clone https://github.com/your-username/feuse-mcp.git
cd feuse-mcp

# Install dependencies
pnpm install

# Build
pnpm build

Add to your MCP client configuration:

Get your Figma API key from Figma Developer Settings.

{
  "feuse-mcp": {
    "command": "npx",
    // Configure path
    "args": ["YOUR/PATH/TO/dist/main.cjs"],
    "env": {
      "FIGMA_API_KEY": "YOUR_FIGMA_API_KEY"
    }
  }
}

📁 Project Structure

feuse-mcp/
├── src/
│   ├── main.ts              # Main entry point
│   ├── services/            # Core services
│   │   ├── figma/          # Figma integration
│   │   ├── similarity/     # Visual comparison
│   │   └── utility/        # Utility toolset
│   ├── types/              # TypeScript definitions
│   └── utils/              # Helper functions
├── docs/                   # Documentation
└── dist/                   # Built files

🤝 Contributing

Contributions are welcome! Feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.

Development Guidelines

  1. Follow the existing code style
  2. Update documentation as needed

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

If you have more interesting, fun, and cool ideas, please submit them in issues immediately ! ! !

🙏 Acknowledgments

  • Figma-Context-MCP for providing Figma design analysis capabilities
  • fastmcp for providing MCP rapid development framework
  • All contributors and users of this project

Alternatives

Related Skills

Browse all skills
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

18
figma-automation

Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.

10
ai-sdk

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

6
api-documenter

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

4
openai-knowledge

Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.

4
cli-builder

Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.

3