Figma gates MCP access, leaves Pi out

Figma is treating MCP like a gated app ecosystem: understandable for protecting sensitive design data, but awkward for a protocol sold on interoperability. Independent agents now face platform approval as a prerequisite for the richest design-to-code workflows.

• –Figma recommends its remote server, which exposes broader capabilities than the local desktop server.
• –Pi’s compatibility problem is OAuth client allowlisting, not a lack of MCP support.
• –The restriction gives approved clients a meaningful feature advantage over open-source agents.
• –Developers building custom agents should plan for catalog submission, local-server fallbacks, or direct API integrations.
• –This sets a precedent for MCP servers to become selectively interoperable rather than universally accessible.