# figma-to-code

MCP server that gives coding agents structured Figma context for design-to-code work

Figma Context MCP is an MCP server for giving coding agents structured access to Figma design context during implementation. Instead of copying screenshots or hand-written design specs into prompts, teams can expose layout, component, and context information to agents such as Cursor, Claude Code, and other MCP-compatible coding workflows. It is a strong design-to-code bridge for teams trying to reduce hallucinated UI details and tighten handoff between designers and AI-assisted developers.

Official remote MCP server for design-to-code and write-to-canvas Figma workflows.

Figma MCP Server is Figma’s official remote Model Context Protocol surface for design-to-code agents. It gives supported clients structured design context, variables, components, selected-frame code context, Code Connect mappings, and beta write-to-canvas tools for creating or updating native Figma frames from an MCP client while keeping the workflow tied to Figma files.

Turn a Figma design system into a programmable API for AI assistants

Figma Console MCP is open-source design-system infrastructure that exposes Figma to AI assistants through MCP. It supports structured extraction, design creation and editing, debugging, accessibility audits, and bidirectional design-token workflows across local, remote read-only, and paired cloud modes; it is not a generic one-click Figma-to-code exporter.

Convert any screenshot or mockup into clean frontend code with AI vision.

screenshot-to-code is an open-source tool that converts screenshots, mockups, and Figma designs into clean, functional HTML, Tailwind CSS, React, or Vue code using AI vision models. Powered by GPT-4V, Claude, and Gemini, it supports video-to-code and iterative editing workflows, making it a rapid scaffolding tool for frontend developers who want to skip the pixel-translation step entirely.