logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·30.10.26
← Back to news

Figma restricts MCP access to whitelisted clients, excluding Pi

Original article
twitter.com|111 points|61 comments|by thdr|Oct 1, 2026

Figma Implements Client Whitelisting for MCP Access, Sparking Controversy

In a recent series of exchanges on X (formerly Twitter) dated September 30, 2026, it was revealed that Figma has placed strict limitations on which clients can connect to its remote MCP (Model Context Protocol) server. Specifically, the AI client Pi is currently excluded from this access.

The Official Stance from Figma

Gayani, representing Figma, confirmed that their remote server is not open to all, but rather operates on a supported list basis.

"You're right that our remote MCP server only accepts clients on our supported list, and Pi isn't on it yet." — Gayani @ Figma

How to Navigate the Restrictions

For those seeking to verify supported clients or request new additions, Figma has provided the following resources:

  • The Official Catalog: View the current whitelist at figma.com/mcp-catalog.
  • Request Form: To advocate for Pi (or other clients), users must submit a request via forms.gle/qSvUawwznWyoj8….

Figma Logo MCP Catalog Preview


Technical Logic & Workflow

The restriction can be viewed as a simple boolean check during the handshake process. In mathematical terms, the access permission PPP can be defined as:

P={1if client∈Whitelist0if client∉WhitelistP = \begin{cases} 1 & \text{if } \text{client} \in \text{Whitelist} \\ 0 & \text{if } \text{client} \notin \text{Whitelist} \end{cases}P={10​if client∈Whitelistif client∈/Whitelist​

The following diagram illustrates the current connection flow:

If we were to represent the server's internal check in a pseudo-code block, it might look like this:

{
  "action": "validate_client",
  "client": "Pi",
  "status": "rejected",
  "reason": "Client not found in supported_list",
  "redirect": "https://figma.com/mcp-catalog"
}

Community Backlash and Philosophical Divide

The decision has not been well-received by the developer community, particularly by those who envision MCP as an open standard.

Key Perspectives

UserSentimentPrimary Argument
David Soria Parra😔 Sad / DisappointedMCP was envisioned as an exclusive open ecosystem.
Matthew Tanous🤨 Confused / CriticalRestricting the "harness" is illogical; compares it to blocking all browsers except Firefox.
Armin Ronacher❓ InquisitiveRequested a detailed explanation for the restriction.

David Soria Parra

David Soria Parra, who created MCP, expressed his hope that Figma would move toward a more transparent and open model, or at the very least, simplify the process for getting onto the allowlist.

Summary of Current Status

The situation remains a point of contention. While Figma maintains its controlled environment, the community pushes for interoperability.

Current Action Items for Pi Integration:

  • Submit request via Google Form.
  • Await review by Figma's team.
  • Update mcp-catalog to include Pi.

Gayani

Post Metrics:

  • Views: 446.8K
  • Engagement: 117 Retweets, 91 Likes, 73 Bookmarks.