What is MCP, and what has Figma opened up?
MCP (Model Context Protocol) is an open standard that lets outside AI agents connect to an application and read and write its data. In Figma's case, an agent can query layout, type styles, color tokens and component structure, then write changes back to the Figma file.
Figma announced 20 new partners this time, and reports named 10 of them. According to Figma's help documentation, supported clients include Claude Code, Cursor, Windsurf, VS Code and Codex. Pricing and a general-availability date have not been published.
What exactly did Dylan Field criticize?
Three things, all quoted. First, on September 30 he noted on X that Anthropic, the creator of the MCP standard, does not expose Artifacts and other cloud resources, and said the open-versus-closed debate ignores asymmetric context sharing. Second, at a media briefing he said MCP "is not a perfect protocol" and "is advantaged more to frontier labs." Third, he said Figma doesn't want to be fully open because exposing more data raises the chance of abuse.
These are his statements. The reports do not mention whether Anthropic responded, so this article does not supply a position for Anthropic.
What does this mean for people using Claude Code with Figma?
Nothing changes directly in the short term. Claude Code was already on the supported-client list in Figma's help documentation, and what you can do today hasn't changed because of this announcement.
The practical caution is that the MCP layer is still being adjusted, with Field himself saying it has plenty of room for improvement, and that pricing and availability dates are unpublished. Use the workflow, but keep a manual fallback and wait for official details on how usage is metered.
How should I treat "open to outside agents" when choosing tools?
Break it into questions you can check one by one: which data an agent can read, which it can write, which data stays closed, what plan or seat is needed, and how usage is metered.
Field's remarks are a reminder that the scope of openness is the vendor's decision and may be narrowed deliberately for risk reasons. Record the scope as it stands when you evaluate, and recheck it periodically rather than assuming it stays fixed.
On October 15, at its first Config event in Bengaluru, India, Figma announced 20 new Model Context Protocol (MCP) partners; US outlets mostly dated their coverage October 14. TechCrunch named 10 of them: Amp, ClickUp, Dia, JetBrains' Junie, Linear, Meta Muse, Mistral, Notion, OpenCode and Sarvam Agents. The list is introduced with "includes," so it may not be complete. MCP is an open standard that lets outside AI agents read and write inside a Figma file: an agent can query layout, type styles, color tokens and component structure, then write changes back to the file.
Startup Fortune's account says Figma opened a narrower version in March with only five partners, focused on turning code into editable canvas objects. This round widens it to 20 new partners, in both scale and purpose. Figma's help documentation lists Claude Code, Cursor, Windsurf, VS Code and Codex as supported clients. Neither report gives pricing or a general-availability date.
What drew more attention than the announcement itself was something Figma co-founder Dylan Field said. On September 30 he posted on X: "I find it interesting that Anthropic (creators of MCP standard) do not expose Artifacts/other cloud resources," and said the open-versus-closed debate ignores asymmetric context sharing. According to TechCrunch, the post came days before Config, after an MCP co-creator complained that Figma didn't support Pi; Field later said Figma plans to support Pi.
At a media briefing in October, Ivan Mehta asked Field about the debate. He said MCP "is not a perfect protocol," with "tons of room for improvement," and that it "is advantaged more to frontier labs." He also said Figma doesn't want to be fully open because exposing more data through MCP raises the chance of abuse; he acknowledged that most users don't intend misuse but said the company still has to weigh the risk. The reports do not mention any response from Anthropic.
Startup Fortune sets this against Canva. At Canva Create on April 16, Canva launched Canva AI 2.0, and COO Cliff Obrecht said the company was moving from "a design platform with AI tools" to "an AI platform with design tools," built on its own model and a relatively closed approach. Figma's approach is an open canvas that lets outside agents edit files through one protocol. That framing is the article's interpretation, not something both companies say.
If your workflow is Claude Code with Figma, this news doesn't change what you can do today: Claude Code was already on the supported list. Two things are worth noting. First, the MCP layer is still being adjusted, and Field himself says it has plenty of room for improvement, so don't tie your workflow to one particular behavior; keep a manual fallback. Second, neither pricing nor a general-availability date has been published, so wait for official details on how Figma meters AI and MCP usage before deciding whether to upgrade a plan for this.
If you choose tools for a team, make "does it let outside agents read and write" an explicit evaluation item, and record the scope: what can be read, what can be written, and what data stays closed. Field's remarks are a reminder that these boundaries are the vendor's decision and can change over time.