Learn what the Figma MCP server is, how it changes the workflow, and how you can use it with SGDS.
MCP stands for Model Context Protocol. It is a standard way for an AI tool to connect to another tool and use real information from it. In the simplest terms, it allows your AI to "see" what you're working on and respond based on that, rather than just your prompt. Instead of guessing, the AI can pull real context and use it to generate more accurate outputs.
Figma first introduced its MCP server to help teams generate code more accurately from Figma screens. Instead of giving AI only a screenshot, teams could give it real design context from selected Figma frames.
This meant the server could pass useful information to the AI, such as variables, components, tokens, and design context—guiding it toward correct outputs instead of generating something that only looks similar.
More recently, the remote MCP server has expanded beyond generating code from selected frames. It can now let agents write directly to the canvas, generate editable designs from live UI, and bring richer design context into the workflow.
Before Figma MCP
Designers usually handed over screens, notes, and links, while developers or AI tools worked from screenshots and manual explanations. That made it easy for design intent to get lost.
When Figma MCP first arrived
With Figma MCP, AI can access design context directly from selected Figma frames instead of guessing from images. With a design system, it can better map components, variables, and layout context—producing more accurate outputs.
What it can do now
AI can work with richer design context, move more fluidly between code and Figma, and even write directly to the Figma canvas.
To set up your Figma MCP server and to turn your Figma designs into working code powered by SGDS components and utilities, you need these things:
Choose your AI agent (Claude Code, Codex, Cursor, etc) and follow their documentation for their installation steps.
Read their documentation for the latest installation steps as their setup instructions are updated frequently. The necessary Figma skills will be installed automatically when you set up the Figma MCP plugin.
Run the following command if you have not have SGDS components installed:
npm i @govtechsg/sgds-web-componentRun the following command to install the skills:
npx skills add govtechsg/sgds-web-componentSelect all existing skills from the list. This pulls the latest skills from the skills/ folder of this repository into your local .agents/ directory, where compatible AI tools automatically pick them up.
Use the workflow that matches your starting point.
Start here if you already have screens in Figma and want the AI to help turn them into SGDS-aligned code or implementation guidance.
Choose the frame or layer you want the AI to work from. Make sure the Figma Dev Mode MCP server plugin is running locally before proceeding.
With the Figma MCP server enabled, give the AI the right Figma context. You can do this in different ways depending on how your MCP setup works:
Be explicit that you want the AI to implement the design using SGDS components and patterns where possible, not just produce generic front-end output.
The agent will read the selected Figma frame via the MCP server, reference the installed SGDS skills to identify the right components and utilities and generate code that replicates the design using <sgds-*> components and SGDS CSS utility classes.
Start here if you send your code back to Figma for further design refinement.
Choose the live page, flow, or section you want to bring into Figma. Tell your AI exactly what should be captured, so it can turn that UI into editable Figma layers.
Tell the AI where the captured screen or objects should go in Figma. If you already know the destination, include the relevant Figma link in your prompt. Here are a few ways you can get it:
Be explicit about what you want sent and where it should go. Ask the AI to map the result to SGDS components, tokens, and layout rules where possible, and to flag anything that does not have a direct SGDS match.
Once the screen is in Figma, tidy the file for future design work. Use clear names, keep the hierarchy clean, and replace temporary UI with SGDS components where possible. When you are ready to turn it back into code, refer to the Figma to code workflow.
The Singapore Government Design System was developed to empower teams in creating fast, accessible and mobile-friendly digital services.