The key facts

  • Figma announced 20 new MCP partners at the Config conference in India
  • Dylan Field: MCP is 'not a perfect protocol,' with lots of room for improvement
  • Field noted that Anthropic does not open its own resources via MCP; Figma also plans to support the Pi tool

20 new MCP partners

At the first Config conference in India, Figma announced an expansion of support for the open MCP standard (Model Context Protocol), which standardizes connecting AI agents to external data sources and tools. The list of new partners includes 20 companies, among them Amp, ClickUp, Dia, Junie from JetBrains, Linear, Meta Muse, Mistral, Notion, OpenCode, and Sarvam Agents.

Criticism of the protocol and polemic with Anthropic

Figma co-founder and CEO Dylan Field had previously expressed doubts about MCP. A few days before the announcement, one of the protocol's creators complained that Figma does not support the open tool Pi. In response, Field wrote on X that he was 'curious' why Anthropic — the creator of the MCP standard — does not provide access to artifacts and other cloud resources via MCP. According to him, the discussion is framed as 'open versus closed,' everyone prefers open, but the problems of asymmetric context exchange are ignored. Later, Field added that Figma plans to support Pi.

Field's position at the briefing

At a media briefing, Field explained that although Figma wants to be open, he does not consider MCP a perfect protocol. 'MCP is not a perfect protocol, and there's tons of room for improvement in it,' he said, adding that the protocol gives more advantages to frontier labs, but he understands users who want to work with Figma data via MCP and supports that.

Caution about openness

Field also explained why Figma does not want to be fully open: the more data the company provides via MCP, the higher the likelihood of abuse. He clarified that most users do not intend to use MCP or Figma data for harm, but the company still must take potential risks into account.