Figma confirms its remote MCP server only accepts whitelisted AI clients

Figma confirms a client allowlist for its MCP server

Figma has confirmed that its remote MCP server only serves a curated set of clients. In a public reply on X dated September 30, 2026, a Figma employee posting as Gayani told a user named David that the company's remote Model Context Protocol server accepts only clients on its supported list, and that Pi — the client David was asking about — is not on that list yet.

The reply directed users to Figma's MCP catalog, the page where the company publishes its currently supported clients, and offered a request form for anyone who wants a new client considered for inclusion.

According to the post's own metrics, the reply had drawn more than 381,000 views, and the exchange was picked up on the Hacker News front page, turning what read as a customer-support answer into a broader discussion about how open Figma's AI integrations actually are.

How the restriction works

Based on the exchange, the mechanics are straightforward: Figma operates a remote MCP server, and that server checks the connecting client against a whitelist reflected in the company's MCP catalog. Clients on the list can connect; clients that are not, like Pi at the time of writing, are refused.

There is a path in, but it runs through Figma. Developers hoping to get a client supported are asked to fill out a nomination form, and Figma decides what gets added. In this exchange at least, the company did not lay out the criteria it uses to evaluate clients or how quickly additions happen.

An allowlist sitting on an open protocol

The Model Context Protocol is an open standard for connecting AI applications to external tools and data sources, and interoperability is central to its pitch: any compliant client should, in principle, be able to talk to any compliant server. Design tools such as Figma have shipped MCP support so that coding assistants and agents can pull structured design data — frames, components, styles — into their workflows.

Figma's whitelist puts a policy layer on top of that openness. The server still speaks the open protocol, but only to clients Figma has approved. That is a notable choice in an ecosystem where many MCP servers accept any authenticated user with a compliant client, and it echoes older platform debates about client-ID gating and who really controls access to a service.

Why it matters

For developers, the practical consequence is simple: building on Figma's MCP endpoints is only viable if your client of choice has made the list. Teams standardised on an unlisted client such as Pi currently have no technical workaround, only a form.

More broadly, the episode is a test case for how the MCP ecosystem develops. If major platforms adopt client allowlists as the norm, the protocol's promise of plug-and-play interoperability will depend less on the standard itself and more on each vendor's approval process — reintroducing a form of gatekeeping that open protocols were meant to reduce. For Figma, the approach offers control over quality, security review and support burden. For everyone building AI tooling around the platform, it means access to one of the most widely used design tools is now granted by the vendor rather than assumed.