Figma's MCP Update Reflects a Larger Industry Shift

I think the blocker is that engineers do not want to take responsibility for the design, and the designer doesn't feel confortable with claude code. But this is a gap that will close soon.

In a recent Claude Code session I tried using the Google Docs, Drive, and Sheets MCP and was honestly surprised at how limited it felt. It was hard to get anything meaningful done because it just did not expose enough capability to be useful in practice. In hindsight, that frustration was probably a good thing. I ended up skipping MCP entirely and using the LaTeX API plus its plugin ecosystem, and the result was far beyond anything I could have realistically produced through Docs anyway.

I have seen a similar pattern with Canva’s MCP. I pay for Pro, but the one feature that would actually make MCP useful, Auto Fill, is gated behind an enterprise plan. So the surface is there, but the real power is locked away.

I get that this is still the wild west for MCP, and I agree with the OP’s general take. But right now there is a big gap between "integration exists" and "integration is actually useful." Personally, I am more excited about where something like WebMCP could go, where the default assumption is full capability rather than a restricted subset.

I attended a design conference last week where Figma has been basically delegated as a design library tool, and that was it. They'd use it as a source of truth for components such as buttons, colors, typography, etc, but the actual design work that was being done was done through Claude Code. Multiple designers who had this stack said that they preferred it as their designs were now closer to what the end user would experience (i.e. code). One person actually eschewed Figma completely and used Storybook as the source of UI truth. I think that Figmas moat is a lot smaller than people think and that within a year or 2 there's going to be some very solid competitors out there.

SaaS products are headed to where the UI isn't the undifferentiated factor. People have been so busy building a UI that works for everyone so it works for no one. The real value is the data and the workflow they provide. Make the data accessible to agents (MCP, OpenClaw skills, etc0.

People who do that will do well.

Completely agree. Every SaaS tool will come with an MCP or an API to leverage composability. We can unlock useful functionalities from Claude Code and other aggregators (terminology from the post) to be able to compose different MCP's from different SaaS. One can imagine composing the results from a google search and using it in for a Figma design attempt, as a simple example.

This is an obvious direction that the industry is heading to. But what are the implications of this? I think the differentiating factor of having a good UI will reduce - productivity apps and SaaS will no longer have their aesthetic UI as a moat. I'm not sure whether this will tank their stocks or increase the valuation but what I'm sure of is that the productivity and usage will increase.

100%. Have been saying for a long time that AI needs data, context and specific capabilities.

Figma offered the capabilities but not the data or context.

Everyone's building "the everything app". The end game is likely an entire OS shell that is AI-first.

Actually... their MCP reflects more than just supporting AI. It demonstrates the future of closed, walled garden MCPs.

While Figma advertises that their official MCP "can now write directly to your Figma files", in reality it is restricted to create and read (as in CRUD), but not update nor delete. Currently, there is only one option to edit/update using the Figma MCP and it requires going through a third-party service with its own subscription and tiny token allocations.

Meanwhile, several developers have figured out how to use Figma's plug-in system to work-around these limitations, for a more robust CRUD MCP solution.

Inter-Op is back! (Limited to AI overlord access only, please don't make our business redundant)

It's so excellent that the walls are coming tumbling down.

Walls and moats are just not viable in the way it used to be: the market tightly demands agency, and it's not something your company can provide solo. The point is that users want to intermix their experiences.

Figma's been super super punished by the market (down from $80 ish ipo in August to $20-$30 since Jan). The faith that AI is somehow is going to build such a mass adopted product that works so relatively well; seems weird. Figma really made strong up front choices to make such strong bones for their work: it feels rare to see companies go for such deliberately chosen high technology web, and it feels like these choices (wasm, multiplayer, etc) have been so core to building such a great business.

[dead]