Figma restricts MCP access to whitelisted clients, excluding Pi

Original Article ↗ Hacker News Discussion ↗

Figma is limiting access to its remote Model Context Protocol (MCP) server to a small set of whitelisted AI clients, blocking popular open-source agents and prompting criticism that this undermines the open, interoperable spirit of MCP. Commenters see the move as part of a broader trend in SaaS and AI: vendors trying to retain control, monetize AI-driven workflows, and protect data by locking down APIs, even as users increasingly expect agents to orchestrate multiple tools freely. Many predict this strategy will backfire as designers and developers either switch to more open competitors or build unofficial workarounds using plugins, REST APIs, or full browser automation.

Whitelisting MCP Clients

  • Figma restricts its remote MCP (which allows document edits) to a vendor allowlist, while the local desktop MCP is read‑only and open to any agent.
  • Many see client whitelisting as contrary to MCP’s open, tool-agnostic intent and worry it fragments the ecosystem.
  • Others note this trend is spreading (e.g., Slack, some LLM providers), suggesting it may become common for commercial tools.

Business Strategy vs. Product Risk

  • Some argue open MCP access “kills” products because it makes it hard to charge for features an LLM can reproduce.
  • Counterpoint: whitelisting may accelerate obsolescence by pushing users toward open, MCP‑friendly alternatives and AI‑driven workflows.
  • Several commenters frame this as “AI subsuming products”: tools become callable back‑end operations rather than primary user interfaces, undermining traditional SaaS moats.

Security, Compliance, and Data Control

  • A security-oriented perspective defends allowlisting as a way to:
    • Control where corporate data flows via MCP.
    • Reduce OAuth redirect / phishing risks for non-expert users.
  • Others call the current mechanism (client name / headers) weak and trivially spoofable, doubting its effectiveness.

Developer Experience, Limits, and Pricing

  • Complaints about:
    • Complex legal/onboarding processes for getting on the allowlist.
    • Dev-seat licensing, low free quotas (e.g., daily call caps), and planned usage-based MCP pricing.
    • Important capabilities exposed only via Figma’s own MCP rather than the public API.
  • Some find the official remote MCP token-inefficient and prefer custom tools over the REST or plugin APIs.

Workarounds and Alternatives

  • Reported hacks: faking the client name to appear as an approved agent, local MCP proxies, reverse‑engineered protocols, plugin shims polled over HTTP, CLI tools masquerading as other clients.
  • Several users advocate switching to or experimenting with alternatives (Pen, Paper, Penpot, Excalidraw, open-source/self‑hosted design tools).

Broader AI & Workflow Trends

  • Multiple comments describe designers and engineers skipping dedicated design tools, prototyping directly in code or via AI agents.
  • Some foresee many existing products being reduced to “bags of tools” orchestrated by external agents, with potential for regulatory responses (e.g., calls for legally mandated open MCP access for key platforms).