Figma co-founder Dylan Field thinks MCP is not a perfect protocol
I like that Figma isn't pretending MCP is the finish line. Field calling it imperfect is a useful corrective to the breathless take that one protocol will rule them all. The realistic read is that the AI integration space is still young, and locking your product to a single standard before the dust settles is a bet most companies shouldn't take.
The interesting part is the data caveat. Figma holds some of the most intimate design work in the industry, and the idea of an AI agent reaching into those files raises real questions about control and privacy. Supporting many standards while gating what gets exposed is a sensible middle path. I'd want to know how they plan to define those boundaries. Deciding what an AI can and can't touch inside a live document is the real work.
Where I land: patience here works in Figma's favor. If MCP wins, they can adopt it fully later. If something better shows up, they haven't painted themselves into a corner.
