#Tag (1)

Framelink MCP for Figma: design files compressed into usable context, not screenshots

Also known as Figma-Context-MCP, npm package figma-developer-mcp, TypeScript, MIT, and a third-party implementation rather than the Dev Mode MCP server Figma ships itself. It exposes only two tools: get_figma_data (read-only) and download_figma_images (removable with –skip-image-downloads, and confined to writing inside –image-dir). The narrow surface is deliberate; the engineering sits in the fetch → simplify → serialize pipeline behind it. Simplify uses composable extractors (layout, text, visuals, component, plus the allExtractors, layoutAndText, contentOnly, visualsOnly and layoutOnly bundles) to compress the raw Figma response into semantic layout and styling in a single tree walk, with maxDepth and nodeFilter, and outputs tree (default, cheapest in tokens), yaml or json. The part worth copying is that compression effectiveness is a metric computed on every call: rawSizeKb against simplifiedSizeKb, rawNodeCount against simplifiedNodeCount, component/instance/text/image node counts, namedStyleCount (the source comment states a high count is a design-system maturity signal), hasVariables (whether Figma Variables are used at all), and separate fetch/simplify/serialize timings; the same hooks drive MCP progress notifications and heartbeats so a large file taking tens of seconds does not look hung. Judgement shows in the details: node IDs accept both the plain and the deeply nested instance shape, the depth parameter description says do not use it unless the user explicitly asks, the proxy default deliberately avoids installing EnvHttpProxyAgent when no proxy variables exist so a stale variable cannot route traffic through an intermediary returning 403, and stdio mode warns at startup when –image-dir is unset. Credentials come from FIGMA_API_KEY or FIGMA_OAUTH_TOKEN; telemetry can be disabled with –no-telemetry or DO_NOT_TRACK=1 and secrets are redacted from reports. 15.9k stars. It generates no frontend code - the output is design facts, and translating them into React, Vue or SwiftUI is your coding agent job. We have not run it against a Figma file of our own and did no screenshot-versus-structured-data accuracy comparison, so it is graded as pending reproduction.