Figma co-founder Dylan Field thinks MCP is not a perfect protocol

At Figma's first Config conference in India, the design company announced 20 new partners for MCP, the Model Context Protocol that standardizes how AI agents connect to external data sources and tools. The partner list includes Amp, ClickUp, Dia, Junie by JetBrains, Linear, Meta Muse, Mistral, Notion, OpenCode and Sarvam Agents. The announcement came alongside public remarks from Figma co-founder Dylan Field, who said the company wants to open up its ecosystem but does not consider MCP a finished standard.
MCP is an open source specification, originally created by Anthropic, that gives AI agents a common way to discover and call external tools and read data. Rather than building a bespoke integration for every assistant, a vendor implements an MCP server once and any compatible client can use it. That is the appeal behind Figma's partner push: a design file, comment thread or component library becomes reachable from whichever agent a team already uses.
Field's reservations are not new. Days before the Config announcement, one of MCP's co-creators complained publicly that Figma was not supporting the open source tool Pi. Field responded on X by questioning why Anthropic does not expose artifacts and other cloud resources created through MCP, writing that the debate gets framed as open versus closed while "issues of asymmetric context sharing are ignored." He later added that Figma plans to support Pi.
At a media briefing, Field elaborated on the tension. He said he is excited about opening the ecosystem, but described MCP as something with "tons of room for improvement" and argued it is "advantaged more to frontier labs." He also acknowledged users who simply want a protocol they can use with their own Figma data, and said he wants them to be able to do so.
Figma's chief executive said the company's reluctance to be fully open stems from risk: the more data Figma exposes through MCP, the greater the chance of abuse. He added that most users have no malicious intent, but the company still has to account for those who might. In practice, this points to a tiered access model, where some Figma surfaces are available to agents broadly and others remain gated, scoped or subject to review. A likely trade-off is that developers building on Figma's MCP server may find certain object types, permissions or bulk operations unavailable, which can push them toward workarounds or toward official connectors from named partners.
Field's "frontier labs" point deserves unpacking. When a protocol's reference implementations and most polished clients come from a handful of well-resourced model vendors, those vendors set the de facto expectations for authentication, tool schemas and context handling. Smaller tool makers and regional players then adapt to choices they had little part in making. The inclusion of India-based Sarvam Agents among the new partners is notable here, since it puts a local model provider in the same integration tier as larger international names.
For teams evaluating the announcement, the practical question is which of the 20 partners ship working Figma integrations and on what timeline, and what scopes each one requests. Figma has not detailed per-partner capabilities in the material available, so the partner names are best read as intent rather than a feature matrix. Developers should also expect the protocol itself to keep shifting, since Field is publicly signaling that he wants changes.
Figma's position mirrors a broader pattern across SaaS platforms. Companies want agent compatibility because it drives usage of their product inside AI workflows, but they also hold back the most valuable or sensitive data, whether for security, rate-limit or competitive reasons. MCP makes the integration cheap; it does not resolve who decides what an agent may see. Governance, audit logging and per-user consent remain the hard parts, and those are exactly the areas Field's "asymmetric context sharing" phrase gestures at.
Why it matters: Product and platform teams building agents on Figma will get more integration options, but likely uneven depth across partners and restrictions on what data is exposed. The debate Field is raising, over whether MCP structurally favors large model vendors, affects anyone choosing to standardize on it. Expect continued pressure from developers for broader access and from vendors for guardrails, and plan for the protocol and its implementations to change under you rather than treating today's integration list as final.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Figma said it plans to support as many standards as possible without exposing all of its data.