Labsco
MCP SERVER

Figma Context MCP

by GLips

Hand a coding agent the layout, content and component data behind a Figma file — and the assets it references — instead of a screenshot of it.

Design Systems & UI Component LibrariesVerified
Summary
A design becomes code from the design's own numbers.

get_figma_data returns the structure rather than a picture of it, so spacing, hierarchy and component names arrive as values an agent can implement against. download_figma_images then fetches the assets that structure points at — the part no screenshot can give you.

What it is

Two calls against a Figma file: one returns its layout, content, visuals and component information, optionally narrowed to a node and a depth; the other downloads the images and icons that file uses.

What you get
  • A Figma file's data by file key — layout, content, visuals and components — or one node of it, to the depth you ask for
  • The image and icon nodes downloaded as SVG or PNG to a local path, with the PNG scale set on the call
Requirements

Npx on your PATH and a Figma API key, passed on the launch line as --figma-api-key. You also need the file key of the file, and node IDs when you want part of it rather than all of it.

Setup effort

One command plus a key — npx -y figma-developer-mcp --figma-api-key=YOUR-KEY --stdio, then supply credentials