A comprehensive Model Context Protocol (MCP) server that bridges Figma designs with AI development workflows. It provides 30 specialized tools for extracting pixel-perfect code, assets, and component structures directly from Figma designs.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"sunnysidefigma-context-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
What if you could talk to your Figma designs and turn them into production code? That's what we built.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in design
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
A mcp server to allow LLMS gain context about shadcn ui component structure,usage and installation,compaitable with react,svelte 5,vue & React Native
AI image generation and editing with prompt optimization and quality presets. Powered by Nano Banana
MCP Security Weekly
Get CVE alerts and security updates for SunnysideFigma Context MCP and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that turns Figma designs into production code. It ships with a companion Figma plugin so LLM clients can read the layer you're actually looking at, extract pixel-perfect CSS and design tokens, and generate React / Tailwind / styled-components output — all from a natural-language prompt.
Two data paths are supported:
getCSSAsync() from inside the editor. Works on any plan, even Drafts.fileKey / nodeId for designs that live in a team/project you can reach with a Personal Access Token.Requirements: Node 18+, a Figma Personal Access Token (create one here).
git clone https://github.com/tercumantanumut/sunnysideFigma-Context-MCP
cd sunnysideFigma-Context-MCP
npm install
npm run build
Create a .env:
FIGMA_API_KEY=figd_your_token_here
PORT=3333
OUTPUT_FORMAT=json
Run the HTTP/SSE server:
npm start
# → http://localhost:3333
# SSE: /sse
# Streamable HTTP: /mcp
Install the Figma plugin (one time):
figma-dev-plugin/manifest.json from this repo.You'll see "Data sent to MCP server successfully" when the bridge is live.
Pick one transport. Both expose the same 27 tools against the same running server.
Use this if you want the client to own the lifecycle and don't need the Figma plugin bridge to share state with the MCP process.
{
"mcpServers": {
"sunnyside-figma": {
"type": "stdio",
"command": "node",
"args": [
"/absolute/path/to/sunnysideFigma-Context-MCP/dist/cli.js",
"--stdio"
],
"env": {
"FIGMA_API_KEY": "figd_your_token_here"
}
}
}
}
The plugin posts extractions to http://localhost:3333/plugin/*. Point your MCP client at the same process so both share the extraction buffer.
{
"mcpServers": {
"sunnyside-figma": {
"type": "sse",
"url": "http://localhost:3333/sse"
}
}
}
{
"mcpServers": {
"sunnyside-figma": {
"type": "http",
"url": "http://localhost:3333/mcp"
}
}
}
These read the buffer filled by the Figma plugin. Fastest, highest fidelity, no API limits.
| Tool | Returns |
|---|---|
get_figma_dev_history | List of past extractions (name, id, layout) |
get_Basic_CSS | Root element CSS via getCSSAsync() |
get_All_Layers_CSS | CSS for every layer in the selection |
get_JSON | Structured: id, fills, variables, design tokens, allLayersCSS — the highest-signal single call |
get_react_component | TypeScript React + CSS module |
get_tailwind_component | React + Tailwind classes (arbitrary values) |
get_styled_component | React + styled-components |
get_plugin_project_overview | Summary of the full scanned project (requires Scan Entire Project in the plugin) |
analyze_app_structure | Architectural breakdown of a scanned project |
Require FIGMA_API_KEY + a file the token can see. Do not work on Drafts — move files to a team/project first.
| Tool | Use |
|---|---|
get_figma_data | Raw file or node JSON |
get_figma_page_structure | Page-level tree for orientation |
get_figma_project_overview | Team/project-level summary |