by f2c-ai
Convert Figma designs into clean HTML & CSS with customizable file paths and organization—fast, accurate code generation
Converts Figma designs directly into HTML, CSS, and React code with pixel-perfect accuracy. Works with selected nodes in the Figma desktop app to generate production-ready code.
Figma to Code is a community-built MCP server published by f2c-ai that provides AI assistants with tools and capabilities via the Model Context Protocol. Convert Figma designs into clean HTML & CSS with customizable file paths and organization—fast, accurate code generation It is categorized under developer tools, design. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.
You can install Figma 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.
MIT
Figma to Code is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
According to our notes, Figma to Code benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Figma to Code is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Figma to Code reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Figma to Code has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend Figma to Code for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated Figma to Code against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Figma to Code into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Figma to Code is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Figma to Code against two servers with overlapping tools; this profile had the clearer scope statement.
Figma to Code has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 71
Due to Figma REST API rate limits, if you are affected, please switch to @f2c/mcp-plugin for normal operation.
English | 简体中文
A Model Context Protocol server for Figma Design to Code using F2C.
<a href="https://glama.ai/mcp/servers/@f2c-ai/f2c-mcp"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@f2c-ai/f2c-mcp/badge" alt="f2c-mcp-server MCP server" /> </a>recommended to use Comate AI IDE
See Configuration and Development
The logging tools integrated in this project are used solely for basic usage statistics and error log reporting. No sensitive information or user data is collected. All reported data is used exclusively to improve product quality and user experience.
See FAQ
Thanks to:
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
