Thread

Figma restricts MCP access to whitelisted clients, excluding Pi

187 points · 106 comments · thdr

miguel-muniz · 1790869419 · focus · HN ↗
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 working.
Kind of strange to limit edit access only to the Remote MCP when their competitors like Pen[1] and Paper[2] allow any local agent to edit.
[1] <a href="https://www.pen.dev/" rel="nofollow">https://www.pen.dev/
[2] <a href="https://paper.design/" rel="nofollow">https://paper.design/
1. miguel-muniz · 1790872749 · focus · HN ↗
  To speak more broadly, Figma is in a really tough spot right now. I see more and more designers in my circle saying they are skipping design tools entirely to prototype in code or ship directly in their product's code base. Honestly I find myself doing the same.
  Figma's main value used to be in providing designers a canvas to iterate and explore ideas since the majority of designers did not code, but AI has completely changed that.
  I fear Figma's reluctance to integrate with all the popular AI tools might actually accelerate their decline. AI provides so much value, that I would rather base my software purchasing decisions around what is compatible with my AI of choice rather than pick an AI that is compatible with Figma.
  1. locallost · 1790874447 · focus · HN ↗
    I think it's really interesting how these areas are merging, and I'm not sure who goes. Designers or "coders". Probably both depending on the context. The expectations though from every field seems to be that they'll be the last man standing. My best guess is, management has the worst cards.
    I am 100% in agreement that companies that try to shut down access to agents will be replaced. It's just the future for a lot of work and workflows. In a way it's an opportunity for someone.
    TeMPOraL · 1790875249 · focus · HN ↗
    > I think it's really interesting how these areas are merging, and I'm not sure who goes. Designers or "coders".
    Neither of them, not yet. What will go away is the products currently used by these groups.
    It's happening in software development, too. In the past 3 months, I used an IDE for maybe few hours total. 99% of my technical work is now easier and better done through agentic chat interface.
    miguel-muniz · 1790876438 · focus · HN ↗
    I struggled with this myself, the reality is that AI can automate the work of everyone in the traditional product team trio (pm, design, dev).
    The way I have made peace with it in my mind is at the end of the day, I am the expert in UI/UX. There are many product teams I've joined that have operated without a designer and you can tell (bless their souls). Component libraries, templates, articles, video courses, and etc. have all existed throughout this time so it's not like they've been operating completely blind to design and UX. I don't think AI would be different. Sure it may raise the floor a little, but in the end someone needs to evaluate the output and hold responsibility for the UI/UX.
    It was an uncomfortable idea to come to terms with though, I like many other designers spent a decade getting good at Figma. Figma and design almost felt intertwined for a moment, but designers have a long history of having their craft disrupted by new technology. Decades ago designers were cutting and pasting paper, then moved to digital publishing; and in product design we've gone through software such as Photoshop, Fireworks, Sketch, and Figma, just to name a few. Design has survived all this and will continue to survive in the future.
    I think the same applies to the other disciplines. Sure I could have AI spin up a backend, but I don't really have the expertise to understand whether what it is doing is good or full of security vulnerabilities.
    I don't know in the future if we will create a new path for product builders, individuals who are knowledgeable in all aspects of product management, software engineering, and product design. I also don't know if teams will have as much need for individuals with the efficiency gains from AI.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.