Figma restricts MCP access to whitelisted clients, excluding Pi
Figma restricts its remote Model Context Protocol server to a whitelisted set of approved clients, excluding open-source AI harnesses like Pi.
summary is enough The short announcement and thread quickly explain Figma's integration limits and the industry-wide friction over AI agent access.
summary
Figma confirmed that its remote MCP server, which provides AI agents write access to design files, only accepts clients from an official whitelist. Developers discovered this blocks open-source AI harnesses like Pi unless they spoof an approved client name like Codex. Commenters argue this represents a broader SaaS panic over AI agents disintermediating proprietary user interfaces and monetization models.
key points
- Figma's remote MCP requires official approval for write access, distinguishing it from read-only local desktop integrations.
- Users found that the whitelist check relies merely on client name strings, which can be easily spoofed.
- Commenters view the restrictions as an attempt by SaaS vendors to protect their ecosystems from open-source agent competition.
who should read it
Software developers and engineers building workflows around AI coding agents and MCP servers.
discussion skeptical
consensus
Commenters widely condemn the restriction as a defensive tactic by SaaS companies trying to control how AI agents interact with their products.
pushback
A few security-minded commenters suggest whitelisting can help mitigate OAuth redirect vulnerabilities and protect corporate data pipelines.
For context: Figma has two MCPs. The local "dev" MCP that works through the Desktop app, and the remote MCP that requires a connection to Figma. Companies need to be whitelisted to use the remote MCP, which is the only one that allows agents edit access to Figma documents.
I only found out about Figma's limitation when I was trying to add the remote MCP server to GitHub Copilot Desktop and kept running into errors. Turns out they whitelisted GitHub Copilot CLI but not the Desktop app and had put a pause on enabling any more vendors. Eventually someone (not sure which side) got it …
It explains the critical functional difference between Figma's local and remote MCPs and points out competing open alternatives.
Generated by an LLM from the article and thread. Check the sources before relying on it.