Figma Expands MCP Ecosystem to 20 Partners Despite Co-Founder's Protocol Critique
By Ali Al-Montaser — Senior AI Technical Editor
Figma announced 20 new MCP partners at its first Config India conference, including Notion, Linear, Mistral, ClickUp, and JetBrains. The expansion comes as co-founder Dylan Field publicly criticizes MCP as imperfect and favoring frontier AI labs. Figma defends restricted data exposure via MCP citing misuse risks, while committing to support open tools like Pi.
Executive Overview
Figma officially announced at its first Config India conference the addition of 20 new partners to its open-source Model Context Protocol (MCP) ecosystem, strengthening the integration of design tools with AI agents. The announcement comes despite explicit criticism from co-founder Dylan Field about the protocol's architecture, reflecting a strategy of "governed openness." The expansion includes major platforms such as Notion, Linear, Mistral, ClickUp, and JetBrains, marking a significant step toward standardizing design data access for AI agents.
📊 Official Technical Specifications & Data Sheet
| Technical Aspect | Confirmed Official Data |
|---|---|
| 💰 Pricing & Usage Cost | MCP is open-source and free to implement; Figma does not charge the announced partners. Actual usage cost depends on the connected model provider (e.g., Mistral or Notion AI), not on Figma. |
| 🌐 Platforms & Immediate Availability | 20 announced partners: Amp, ClickUp, Dia, Junie from JetBrains, Linear, Meta Muse, Mistral, Notion, OpenCode, Sarvam Agents, and others. Available via standard MCP interfaces for the Figma platform. |
| ⚡ Performance & Speed Benchmarks | No official benchmark figures were published in the announcement; the core value is expanding the number of integration points through a unified standard protocol. |
| 🛡️ Security & Breach Resistance | "Governed openness" approach: the more data exposed via MCP, the higher the risk of misuse according to the CEO, so permissions are restricted to reduce the attack surface. |
| 🧠 Context Window | Depends on the model connected via MCP, not on Figma; Figma does not impose a unified limit, but it is subject to the context size of the model provider (Mistral, Notion, Linear, etc.). |
| 🌍 Arabic Language & Regional Support | The announcement was made at Config India, reflecting a focus on emerging markets; Arabic support depends on the partner model (e.g., Sarvam Agents specialized in Indian languages) and there are no official statements regarding dedicated Arabic support. |
Deep-Dive Features & Architecture
The announcement took place at the first Config conference held in India, where Figma unveiled the list of 20 new MCP partners, including Notion, Linear, Mistral, ClickUp, OpenCode, Dia, Amp, Meta Muse, Junie from JetBrains, and Sarvam Agents. This expansion represents a practical step toward making Figma design data available to AI agents through a unified standard interface, rather than building custom integrations for each tool individually.
However, the announcement coincided with public controversy over the protocol's transparency. Days before the conference, a participating MCP developer criticized Figma for not supporting the open-source Pi tool. Dylan Field responded on X, saying: "I find it interesting that Anthropic (the creator of the MCP standard) does not disclose the artifacts or other cloud resources created via MCP," adding that the debate is framed as open vs. closed while issues of "asymmetric context sharing" are ignored. He later confirmed that Figma plans to support Pi.
In a media briefing, Field explained that MCP "is not a perfect protocol and has wide room for improvement, and it gives a greater advantage to frontier AI labs," while the CEO justified the lack of full openness by stating that increasing data exposed via MCP raises the likelihood of misuse, acknowledging that most users do not intend harm.
Benchmark & Competitive Performance
No standard benchmark figures or specific performance improvement percentages are available in the announcement. The core comparison lies in the governance model: while Anthropic pushes MCP as a fully open standard, Figma adopts a hybrid model that expands partnerships (20 new partners) while restricting exposure of sensitive data. This approach may reduce the risk of design data leaks, but it could also limit the depth of integration expected by some open tools like Pi, positioning Figma as balancing openness and security rather than competing on raw performance numbers.
Industry Impact & Enterprise Adoption
For enterprise users, the expansion of MCP partners means that tools like Notion, Linear, and Mistral are now closer to integrating with Figma design outputs through a single standard interface, reducing the need for custom connectors. This standardization can accelerate workflows in product design and development, enabling AI agents to access design context more seamlessly. However, the restricted data exposure may require enterprises to evaluate security policies and access controls when deploying MCP integrations. The move also signals Figma's commitment to supporting open-source tools like Pi, which could foster broader community adoption and innovation.
Conclusion
Figma's expansion of its MCP ecosystem to 20 partners underscores its strategic push to integrate design tools with AI agents, even as co-founder Dylan Field openly critiques the protocol's limitations. The company's "governed openness" approach balances the benefits of standardization with security concerns, but it remains to be seen how this affects deeper integrations with open-source tools. For now, the announcement solidifies Figma's role in shaping the future of AI-driven design collaboration.
Media Source: TechCrunch AI | Fact Verification & Analysis: AI Tools Oasis
Frequently Asked Questions
Figma announced 20 new partners for the Model Context Protocol (MCP) at its first Config India conference, including Amp, ClickUp, Dia, Junie from JetBrains, Linear, Meta Muse, Mistral, Notion, OpenCode, and Sarvam Agents.
Figma co-founder Dylan Field stated that MCP is not a perfect protocol and has wide room for improvement, and that it gives a greater advantage to frontier AI labs compared to other players.
Figma's CEO explained that increasing data exposed via MCP raises the risk of misuse, so the company takes a cautious approach even while acknowledging that most users do not intend harm.
Yes, after a debate on X, Dylan Field confirmed that Figma plans to support the open-source Pi tool, responding to criticism from an MCP developer.
Figma's first Config conference was held in India, the event where the official announcement of 20 new MCP partners took place.

AI Tools Oasis Team
Bringing you the latest news and analysis in the world of Artificial Intelligence with accuracy and credibility. Follow us for all updates.
