# Figma added 20 MCP partners without exposing everything. Scope your own server the same way.

*2026-10-22 ⬩ 8:00 AM ET | bryn*

Figma announced 20 new MCP partners this week while co-founder Dylan Field held some of its data back, and that's the right default for any MCP server you ship. MCP, the Model Context Protocol, lets an agent call another company's tools and data. Field, Figma's co-founder and CEO, told [TechCrunch on Oct 20](https://techcrunch.com/2026/10/20/figma-co-founder-dylan-field-thinks-mcp-is-not-a-perfect-protocol/) that the protocol "is advantaged more to frontier labs." His reason for holding data back was plainer. The more Figma exposes, the higher the chance of abuse.

I read that as a scoping rule, not a protocol fight. Open versus closed makes a lively thread. It doesn't tell you what goes behind a tool call. Start from the jobs an outside agent needs done. Expose those, and nothing next to them. Add a resource when a partner asks for it with a reason. Log who calls what, so the next scoping call has evidence.

Most small teams ship their first MCP server by wrapping the whole API. It's the fastest version. It's also the hardest to walk back once agents depend on it. Figma added 20 new partners without opening everything. Your server can grow the same way, one job at a time.

## Sources

1. [Figma co-founder Dylan Field thinks MCP is not a perfect protocol](https://techcrunch.com/2026/10/20/figma-co-founder-dylan-field-thinks-mcp-is-not-a-perfect-protocol/). TechCrunch, Oct 20, 2026.

See also: https://www.civic.com/field-notes/your-vendors-ship-mcp-servers-now

Source: https://www.civic.com/bin/figma-holds-some-data-back