Figma pushes design context beyond the canvas
Figma is expanding how its design data can be accessed by tools outside its own ecosystem. The company announced updates to its Model Context Protocol (MCP) server and Code Connect that let developers and AI agents pull structured design information directly into IDEs, coding agents, and other applications.
The core idea is that design context—how a design system is structured, how components map to code, and how teams build products—should not be trapped inside design files. With these updates, that context becomes portable, whether a team is working in a code editor, prototyping, or using an AI assistant.
Remote access to design files
The Figma MCP server, first introduced as a local beta in Dev Mode, now supports remote access. This means teams can connect to Figma from the browser, an IDE, or any AI-powered coding tool without needing the Figma desktop app.
Because Figma files store more than static images—they contain responsive layout rules, interaction details, and sometimes entire visual programs—this context can inform code generation in ways that plain screenshots cannot. The update opens Figma connections to new partners including Android Studio, Replit, and Warp.
Setup is simpler as well. A new partner catalog lets users find their IDE or agent of choice and integrate the Figma MCP server directly. Alternatively, integration can be initiated from inside the MCP client itself. Figma says it will continue adding tools and partners throughout the beta period, following up on an earlier addition that generates design system rules.
Bringing Make files into the loop
The MCP server now also works with Figma Make, the company's tool for faster prototyping and idea exploration. When a Make file is accessed via an MCP client, AI models can read the underlying code rather than a rendered image or prototype.
Under the hood, the MCP server indexes the code within a Make file, so developers or AI agents can pull exactly the snippets they need—reusing code directly from a specified file or drawing on the file's logic and patterns as reference. The experience is available immediately with partners such as Anthropic, Cursor, Windsurf, and VS Code.
Mapping components without the CLI
Code Connect, Figma's system for aligning codebase components with Figma components, gains a new in-app mapping interface. Previously, defining those relationships required working from the terminal. Now users can browse components inside Figma, assign them to the correct code and file, and review at a glance which components are connected and which are missing.
The new interface complements the existing Code Connect CLI, which developers use to push production-ready snippets into Dev Mode with prop and variant mappings for most frameworks. Many organizations are adopting both setup methods.
Using Code Connect alongside the MCP server adds production awareness to the design context that AI agents receive. Early internal evals and tests with alpha customers reported more consistent code output, faster file navigation, and better token efficiency from AI agents when both tools were in play.
Stricter integration vetting
With more ways to connect Figma to external tools, the company is also tightening the review process. All public third-party integrations and MCP clients will now be reviewed by Figma before they can access user data, similar to how plugins and widgets are vetted. The REST API rate limits are being adjusted for a more predictable experience for app builders.
These changes take effect November 17 and will affect fewer than one percent of Figma's active users.
A two-way street ahead
Today's releases—remote MCP access, Make file support in the MCP server, and in-app Code Connect setup—are the first step in a broader plan. Figma's long-term goal is for context to move freely in both directions, allowing external tools to feed information back into Figma. That would mean more realistic prototypes, fewer rebuilds, and less time spent translating between design and code.
These features are all in beta now. Design files, the company argues, are more than references; they are inputs containing accumulated knowledge about how a product should be built.
