Figma clarified that its remote MCP server only accepts clients that appear on a maintained supported-list, and that Pi is not currently included. Gayani, a Figma representative, pointed people to the MCP catalog on Figma’s site and provided a form to request that Pi be considered for future addition. The message makes the policy explicit: access is controlled by an allowlist and additions require going through Figma’s intake process rather than automatic compatibility.
That announcement prompted pushback from developers who framed MCP as intended to be an open ecosystem. Critics argued that server-side client whitelisting is an unnecessary restriction - one compared it to only allowing a single browser to visit a website - and urged Figma to either open access or vastly simplify the allowlist process. Others noted incremental improvements in MCP tooling but said the current restriction feels like a step backward for openness, while some asked Figma to explain the technical rationale for client-specific blocking.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.