● BREAKING NEWS
Logo
Select Language
search
AI Oct 20, 2026 · min read

Figma MCP Warning Issued by Co-Founder Dylan Field

Figma co-founder Dylan Field says MCP is not a perfect protocol, as the company plans to support as many standards as possible without exposing all its data.

Civic News India

Civic News India

Civic News India

Figma MCP Warning Issued by Co-Founder Dylan Field

TL;DR — Quick Summary

Figma co-founder Dylan Field says MCP is not a perfect protocol. Figma plans to support as many standards as possible while keeping all of its data from being exposed.

Key Facts
Who
Dylan Field, co-founder of Figma
His view
MCP is not a perfect protocol
Company plan
Figma plans to support as many standards as possible
Data stance
Figma does not want to expose all of its data
Topic
Standards support and data exposure at Figma

Figma co-founder Dylan Field has said that MCP is not a perfect protocol. His comment comes as Figma works out how it will support outside standards. The company says it plans to support as many standards as possible. At the same time, it does not want to expose all of its data.

What Dylan Field Said About the MCP Protocol

Field's point is simple: MCP works, but it is not flawless. He did not describe it as a finished or ideal standard. For Figma, that matters because the company has to decide how it connects its platform to outside tools and systems.

The original story states that Figma plans to support as many standards as possible. That means the company is not putting all its weight behind one protocol. It wants to stay open to different standards rather than tie itself to a single one.

Figma's Plan to Support Multiple Standards

Figma's approach has two parts. First, support as many standards as possible. Second, do not expose all of its data in the process. The two goals sit together, and they explain why Field is careful about calling any single protocol perfect.

  • Figma plans to support as many standards as possible
  • Figma does not plan to expose all of its data
  • Field's position is that MCP is not a perfect protocol

To put it plainly, Figma wants flexibility on the outside and control on the inside. It will connect to standards, but it will decide how much data goes out.

Our Take: Why Field's Comment Matters

In our view, Field is being honest about a real trade-off. Calling a protocol "not perfect" is not a rejection. It is a signal that Figma will not hand its platform and its data over to one standard just because it is popular.

For readers who use Figma or build tools that connect to it, the message is clear. Expect broad standards support, but do not expect full data access. Figma is keeping a gate on its own data, and Field's comment about MCP shows the company is thinking carefully about how open it should be.

That is a sensible position. A protocol can be useful and still have gaps. The company that admits this early is usually the one that avoids bigger problems later.

Civic News India

Written by

Civic News India

Senior Reporter