Figma co-founder Dylan Field thinks MCP is not a perfect protocol
- ID
- 37417
- Status
- summarized
- Published
- 20 Oct 2026, 10:13 PM
- Fetched
- 21 Oct 2026, 1:44 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/10/20/figma-co-founder-dylan-field-thinks-mcp-is-not-a-perfect-protocol/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 6.0
- Created
- 21 Oct 2026, 1:45 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
At its first Config conference in India, Figma announced 20 new MCP partners, including Amp, ClickUp, Linear, Mistral, Notion, OpenCode, and Sarvam Agents. Figma co-founder Dylan Field said MCP is "not a perfect protocol" with "tons of room for improvement" and is "advantaged more to frontier labs," while also noting that Anthropic does not expose artifacts or other cloud resources via MCP. Figma later said it plans to support Pi.
Why it matters
If you build agent workflows that pull Figma data, the 20-partner list is a concrete integration menu, but Field's "asymmetric context sharing" critique means you should test what each MCP server actually exposes—design files only, or cloud artifacts and write actions too—before assuming open-protocol support means equal access. For SaaS and design-tool founders in this audience, the practical takeaway is to define explicit MCP read/write scopes rather than treating MCP support as a checkbox.
Discussion angle
Which of these 20 MCP integrations would builders actually use—reading Figma files, writing comments, or triggering code generation—and does Field's "asymmetric context" complaint change how you evaluate MCP servers from frontier labs?