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": {
"sunnyside-figma": {
"env": {
"FIGMA_API_KEY": "figd_your_token_here"
},
"args": [
"/absolute/path/to/sunnysideFigma-Context-MCP/dist/cli.js",
"--stdio"
],
"type": "stdio",
"command": "node"
}
}
}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.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
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
Swirl Design System AI package with artifacts for AI agents
GoPeak — The most comprehensive MCP server for Godot Engine. 95+ tools, LSP, DAP, screenshots.
shadcn/ui for Laravel Blade — discover, read and install BlatUI components, blocks and charts.
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 |