Design & ProductARTICLE

Figma's Dev Mode MCP Server Gains Access Control and More Context for Code Agents

Figma's November 2026 release notes show the MCP Server maturing: an OAuth allowlist for administrators, prototype connections turning into context for the agent, and GitHub repositories entering the flow by default.

Figma's Dev Mode MCP Server Gains Access Control and More Context for Code Agents
Image: Yara Uchôa
Article · Design & Product
Reading
5 min

Figma's November 2026 release notes show the MCP Server maturing: an OAuth allowlist for administrators, prototype connections turning into context for the agent, and GitHub repositories entering the flow by default.

Figma's Dev Mode MCP Server is the feature that lets code agents like Cursor and Claude Code connect to Figma design files, serving as an alternative to screenshots or manually exported specs. What Figma's official release notes show now, in November 2026, isn't a relaunch of the server, but a series of adjustments that change who can use it and with what quality of context it delivers the file to the agent.

For those who make handoff decisions every day, these changes matter more than they seem: they shift part of the responsibility for "preparing the file for AI" away from each individual designer and onto the team's governance and the structure of the file itself.

Who Can Plug In What: the OAuth Allowlist

Since November 17, 2026, administrators of teams on Organization and Enterprise plans can maintain an allowlist of approved OAuth applications, including MCP clients like Cursor and Claude Code. Management lives in a new tab called Extensions, inside the admin console, where the administrator reviews access requests and decides which apps the team can connect to Figma.

In practice, this takes the decision to authorize a new MCP client away from the individual designer. Before, it was enough for the developer to set up the MCP Server in their own code editor and request access to the file; now, on Organization and Enterprise accounts, that access may depend on prior approval from the administration team. It's a corporate security adjustment, not a design product one, but it can stall the handoff flow if no one warns the administrator ahead of time.

In short: before promising a team that the agent will read Figma directly from the editor, it's worth confirming whether the plan is Organization or Enterprise and, if so, whether the MCP client is already on the allowlist.

Prototype Becomes Context, Not Just Appearance

As of November 3, 2026, when someone creates a code layer (still in open beta) from design frames, Figma's agent also starts reading the prototype connections and interactions between those frames. This means the agent doesn't just see the position of elements on screen: it sees that button A leads to frame B, and uses that to build the flow logic instead of relying solely on the prompt written by whoever is requesting the code.

For those who work with interaction-rich prototypes, this is the kind of information that historically got lost in traditional handoff. Specs exported as PDF or screenshots never carry the connection "on this click, go to that screen"; Figma's prototype does, and now that information enters as direct context for the generated code, reducing the part of the prompt the dev would otherwise have to write by hand to describe navigation flows and screen states.

The Shortcut That Skips Dev Mode

The launch of the 3D transform effect, on November 12, 2026, brought another detail relevant to anyone thinking about MCP: after finishing a 3D composition, the person can copy the CSS through Dev Mode as they always did, or send the design straight to the code agent using Figma MCP, without going through the intermediate step of generating specs in Dev Mode first.

This confirms a direction that was already taking shape: Dev Mode and the MCP Server stop being two parallel paths and become different exit points of the same pipeline. One serves those who want to copy ready-made values (CSS, tokens); the other serves those who want the agent to interpret the entire structure and generate a component, not just style.

GitHub Connected by Default

Also on November 3, 2026, Figma started automatically cloning connected GitHub repositories by default for new repository connections, eliminating the extra administrator-approval step that existed before. Existing connections keep the previous configuration, and administrators can still disable cloning repository by repository at any time.

This change matters because Code Connect and the MCP Server's agents depend on Figma being able to see the actual source code of components in order to map design to implementation. With automatic cloning, the initial setup friction drops, but teams with sensitive repositories (customer data, keys in configuration files mistakenly versioned) need to review whether they want this default behavior turned on.

Checklist Before Connecting an Agent to the File

Before opening an MCP client on a real project, it's worth running through a quick check:

  1. Confirm the plan and the allowlist. On Organization or Enterprise accounts, check with the administrator whether the MCP client (Cursor, Claude Code, or another) is already approved in the Extensions tab.
  2. Name layers with intention. A layer name like "Group 47" doesn't become useful context for the agent; a name like "CardProduto/Botão-Comprar" does.
  3. Map the components in Code Connect before asking the agent to generate code, so it points to the actual design system component instead of recreating a new one from scratch.
  4. Review the prototype connections for flows that will become code layers: interactions without a clear destination or with multiple triggers confuse the agent just as much as they would confuse a human dev reading the prototype for the first time.
  5. Check repository cloning in the admin console if the project involves sensitive code, and disable it manually if the team doesn't want GitHub cloned by default.
  6. Document accessibility states and variants (focus, alt text, reading order) directly in the file: none of these updates teach the agent to infer accessibility semantics that aren't explicit in the design.

What MCP Still Doesn't Solve

None of November's changes touch the point that most worries anyone thinking about accessibility: the agent reads visual structure and, now, prototype connections, but it doesn't read intent for keyboard use, reading order for screen readers, or contrast designed for low vision, unless that's already annotated in the file in some format readable by the API. Dev Mode and the MCP Server speed up the translation from design to code; they don't replace the human decision about which focus states, ARIA labels, and heading hierarchy the final component needs to have.

Code layers remain in open beta, which means behavior subject to change, and the OAuth allowlist is "rolling out" to Organization and Enterprise accounts over the coming days, according to Figma itself, with no completion date announced. Before building a definitive playbook for AI-assisted handoff, it's worth treating these two pieces as still in motion.

Translated from the Brazilian Portuguese original · Read the original

View profile →