Figma Adds 20 MCP Partners While Its CEO Calls the Protocol Flawed

By Grace Kim

Figma announced 20 new model context protocol (MCP) partners at its first Config conference in India — days after co-founder and CEO Dylan Field publicly called the standard imperfect.

The new partners include Amp, ClickUp, Dia, Junie by JetBrains, Linear, Meta Muse, Mistral, Notion, OpenCode and Sarvam Agents, the design company said at the event.

That's a strange pairing on its face: a company expanding support for a protocol its own CEO has doubts about. The tension started playing out in public before the conference.

What did Dylan Field say about MCP?

Days before the announcement, one of MCP's co-creators complained that Figma did not support the open-source tool Pi. Field pushed back on X, pointing a finger at Anthropic, the company behind the MCP standard.

"I find it interesting that Anthropic (creators of MCP standard) do not expose artifacts / other cloud resources created via MCP," Field wrote on X. "The debate is framed as open vs closed. Everyone always prefers open… obviously. And meanwhile issues of asymmetric context sharing are ignored."

Field later added that Figma plans to support Pi.

At a media briefing, I asked Field about this debate. He was blunt: Figma wants openness, but he doesn't think MCP is a perfect protocol.

"I'm really excited about what we're doing in terms of opening up our ecosystem. I also think that MCP is not a perfect protocol. And I think that it is something that has tons of room for improvement," Field said. "It is advantaged more to frontier labs. Also, I understand everyone online who just wants a protocol that they can use when they want to use their Figma data, and I want them to use it, too."

In plain words: Field backs the ecosystem play, not the protocol's design.

Why won't Figma go fully open?

Field explained the company's hesitation in one word: abuse. The more data Figma exposes through MCP, the higher the chance of that data being misused.

He added a caveat. Most users don't intend to use MCP or Figma data maliciously. Even so, the company still has to weigh those potential risks before opening the taps further.

The takeaway is simple: Figma is betting on MCP's ecosystem while hedging on its security — and Pi support is coming.

The 20-partner expansion shows where Figma's commercial logic sits: interoperate now, fix the protocol's flaws through pressure and usage rather than withdrawal.