Figma Restricts MCP Access to Approved Clients

Figma has restricted its remote Model Context Protocol (MCP) server to a curated list of approved clients, a decision that has sparked debate over the openness of the emerging AI integration standard. The restriction was confirmed by Figma representative Gayani, who noted that the company's server only connects with platforms on its official supported list.

Currently, the whitelist excludes several tools, including the Pi client. Figma has directed developers to its official MCP catalog at figma.com/mcp-catalog to view the currently supported integrations. For developers who want to use excluded clients like Pi, the company has provided a Google Form to submit requests for future consideration.

This gatekeeping approach has drawn criticism from the developer community, including the creator of the protocol. Expressing disappointment on social media, the creator stated that they designed the protocol to foster a free and open ecosystem. They argued that restricting server access based on the specific client harness makes little sense, comparing the policy to a website that blocks all web browsers except for Firefox.

For AI practitioners and software engineers, this restriction changes how they can interact with Figma's design data. The Model Context Protocol was built to allow seamless, universal communication between AI models and external data sources. By requiring clients to be whitelisted, Figma introduces administrative friction for teams building custom AI assistants or using niche tools. Instead of immediate interoperability, developers must now wait for official approval, potentially slowing down the deployment of tailored design automation workflows.