Watch condition: Look for documentation specifying which Figma objects and actions Delta and Zed can access through MCP, and whether design-system guidelines and code sources are available to those integrations.
This is a distinct analytical record because no prior New Runtime record was supplied for this specific MCP partnership and its connection to Figma’s newly described context workflows.
Thesis
Design tools are turning their canvases and system rules into context surfaces that coding agents can consume, rather than treating design as a static handoff artifact.
Observed facts
Figma’s October 15, 2026 post says code layers entered open beta on all plans, enabling teams to explore code-backed prototypes on the canvas.
1It says design-system guidelines entered open beta and code sources from GitHub repositories or npm packages began in closed beta on paid plans.
1A separate supplied announcement says Figma is partnering to bring Figma to Delta and Zed via MCP, but gives no capability or rollout details.
1
Mechanism
Figma describes Specs as a shared context container that can reference decisions and work across diagrams, designs, and code layers; its MCP server can send that context to coding agents. The practical change is a more structured handoff: agents can be given reusable design rules and code sources, while teams inspect code-backed results in the design environment.
Why now
The announcement explicitly frames these launches around teams increasingly building with agents, when producing prototypes is easier but preserving shared context and collaboration is harder.
Implications
Design-system rules and code sources can become inputs to agent work, potentially reducing drift between generated interfaces and a team’s established patterns.
The MCP partnership also suggests that this context may move across more than Figma’s own interface, though the named integration’s exact scope remains unreported.
Evidence boundary
The supplied Figma blog is a company description of its products and availability. The separate partnership announcement names Delta, Zed, and MCP only; it does not establish supported operations, rollout dates, or whether all Figma features are exposed. This evidence supports a product-direction reading, not a measured claim about quality or adoption.
Watch conditions
Look for documentation specifying which Figma objects and actions Delta and Zed can access through MCP, and whether design-system guidelines and code sources are available to those integrations.