Figma expands MCP support despite co-founder's protocol concerns

Figma adds 20 MCP partners while its co-founder argues the standard favors frontier labs and risks asymmetric context sharing.

Threat Times Systems DeskOctober 20, 20262 min read

Share LinkedIn Reddit

Illustration: A sleek design interface with abstract geometric shapes floats above a tangled network of transparent data tubes. — AI-generated illustration: Threat Times

Key points

Figma announced 20 new Model Context Protocol partners at its Config conference in India.
Co-founder Dylan Field stated MCP is not a perfect protocol and benefits frontier labs.
The company limits data exposure via MCP to reduce the risk of abuse.

Figma announced the addition of twenty new partners for the Model Context Protocol at its first Config conference held in India. The design company is expanding its support for the open source standard that allows AI agents to connect to external data sources and tools. This move occurs despite public reservations expressed by the company’s leadership regarding the protocol’s current state and potential risks.

The new partners include Amp, ClickUp, Dia, Junie by JetBrains, Linear, Meta Muse, Mistral, Notion, OpenCode, and Sarvam Agents. According to TechCrunch, Figma plans to support as many standards as possible without exposing all of its data. This strategy aims to balance ecosystem openness with security concerns about how much information is shared through these connections.

Protocol concerns and industry dynamics

Figma co-founder Dylan Field has previously expressed misgivings about the Model Context Protocol. He stated that while he is excited about opening up the ecosystem, he does not consider MCP a perfect protocol. Field argued that the standard has significant room for improvement and is currently advantaged more to frontier labs. He also noted that issues of asymmetric context sharing are often ignored in the debate between open and closed systems.

Field highlighted that Anthropic, the creator of the MCP standard, does not expose its own artifacts or cloud resources via the protocol. He wrote on X that everyone prefers open systems, but the reality of data exposure is complex. Following complaints from one of MCP’s co-creators about Figma not supporting the open-source tool Pi, Field added that Figma plans to support Pi. This clarification came after he pointed out the inconsistency in Anthropic’s own use of the standard they created.

Data exposure and security risks

During a media briefing, Field explained that Figma’s reluctance to be fully open stems from security considerations. The CEO stated that the more data the company exposes through MCP, the higher the chance of abuse. While most users do not intend to use MCP or Figma data in a malicious way, the company must account for those potential risks. This cautious approach reflects a broader industry tension between interoperability and data protection.

Field acknowledged that users want a protocol they can use to access their Figma data, and he supports that goal. However, he emphasized the need for careful implementation to prevent unintended consequences. The company’s decision to announce new partners while voicing criticism suggests a pragmatic approach to adopting emerging standards. Figma aims to participate in the ecosystem while maintaining control over how its data is accessed and used by third-party AI agents.

What should you do?

Security professionals should monitor Figma’s implementation of MCP to understand how data is shared. Review access controls for any AI agents connecting to design tools. Watch for updates on how Figma handles asymmetric context sharing. Evaluate the risks of exposing sensitive design data through new integrations. Ensure that third-party partners comply with your organization’s security policies.

What to do and how to stay safe: Figma

Audit all third-party integrations that use the Model Context Protocol to ensure they align with your data governance policies.
Review access permissions for AI agents connecting to Figma to limit exposure of sensitive design assets.
Monitor vendor announcements for changes in how data is shared via MCP, particularly regarding asymmetric context sharing.
Verify that any new partners added to your ecosystem have undergone proper security vetting before granting access.

Step-by-step guide: Mobile Device Security: How to Protect Data Beyond Passwords

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Why is Figma cautious about the Model Context Protocol?

Figma co-founder Dylan Field stated that MCP is not a perfect protocol and favors frontier labs, while also raising concerns about asymmetric context sharing and abuse risks.