The partnership list
The new partners include Amp, ClickUp, Dia, Junie by JetBrains, Linear, Meta Muse, Mistral, Notion, OpenCode and Sarvam Agents.
The expansion sits alongside a dispute over what openness should mean in practice. Days before Figma’s announcement, one of MCP’s creators criticized the company for not supporting the open-source tool Pi. Field replied that Anthropic does not expose access to various resources through MCP either. He later said Figma planned to support Pi.
On X, Field argued that the debate was being framed as open versus closed, while a more practical issue went unaddressed: an imbalance in how much context each side shares. He pointed to MCP’s creators not making artifacts and other cloud resources available through the protocol.
Openness has a limit
At a press meeting, Field said Figma wants to open its ecosystem but does not consider MCP a perfect protocol and sees considerable room for improvement. He also argued that the standard gives an advantage to leading labs. Still, he understands why users want a protocol for working with Figma data—and said he wants them to use one.
Figma’s CEO offered a separate reason for restraint: exposing more data through MCP increases the chance of abuse. Most users, the CEO said, are not trying to misuse MCP or Figma data, but the company still has to account for that risk.
My read is that Figma’s position is less a rejection of MCP than a refusal to treat access as an all-or-nothing choice. The announcement names 20 partners, but it does not say what data they can reach, how much context they receive, or how Figma will draw the line between useful access and exposure. Those details matter more than the partner count: without them, “open” describes an intention, not the terms of the exchange.
Daily AI news
Every day we pick what actually matters in AI and explain it plainly — no hype, no filler. Subscribe if you want to follow where the industry is going.
Only what matters — every day
Follow on X