Overview
What is Codigma MCP Server?
Codigma MCP Server is the backend service behind Codigma.io, a free tool that turns public Figma links into clean, semantic HTML and CSS. It provides API endpoints to fetch Figma file data, convert designs to structured models, and generate HTML/CSS or TailwindCSS bundles.
How to use Codigma MCP Server?
Clone the repository, install dependencies with npm install, create a .env file with your Figma Personal Access Token, then run in development mode (npm run dev) or production mode (npm run build && npm start). Send POST requests to endpoints like /api/figma-to-bundle with a Figma URL and output type (plain or tailwind).
Key features of Codigma MCP Server
- Fetch public Figma file JSON data
- Convert Figma nodes into structured Codigma Models
- Generate clean, semantic HTML and CSS code
- Optionally generate TailwindCSS class-based HTML
- Support for responsive design, fonts, borders, shadows, and gradients
- Full pipeline from Figma URL to code bundle in one API call
Use cases of Codigma MCP Server
- Rapidly prototype web pages from Figma designs
- Automate conversion of design libraries into reusable HTML/CSS components
- Integrate Figma-to-code conversion into CI/CD pipelines
- Generate TailwindCSS HTML from Figma links for utility-first projects
- Build no-code tools that produce production‑ready markup from design files
FAQ from Codigma MCP Server
What does Codigma MCP Server do that alternatives don’t?
It is a free backend service that directly converts public Figma links into clean HTML/CSS or TailwindCSS, all through a simple API. It bundles the full process (fetch, model, generate) into a single endpoint.
What are the runtime requirements?
Node.js 18 or later, npm, and a Figma Personal Access Token stored in a .env file.
Does it work with private Figma files?
Currently, only public Figma files are supported. OAuth login for private files is on the roadmap.
What transports and authentication are supported?
The server uses HTTP/HTTPS with API endpoints accessible via POST requests. Authentication is handled via a Figma Personal Access Token, not via the MCP server itself.
Where does the data live?
Data is processed on the server and returned in the API response; the server does not store design data permanently.
