Skip to content
Bookmarkit
All news
Figma|Update··Abhishek Kapoor

Figma’s 1 September shader and plugin update is an MCP handoff story

The Figma design agent can now publish generative plugins and animated shaders, and the MCP server can read and write that code. The useful question is who owns the file after the agent builds it.

A design canvas fragment dissolving into layered code panels, with a soft shader wash across the surface
Summarize this page with AI

On 1 September 2026, Figma product designer Rogie King wrote that generative plugins and shaders gained four things that matter for a shortlist: community or organization publishing, animated and mouse-reactive shaders, downloadable source, and MCP tools that let an outside agent view and change those files.

Config 2026 already showed an agent that could build a plugin or a shader on the canvas. This release is the handoff. A designer can keep the artifact in Figma, or an engineer can pull the code into Claude Code or another MCP client and push a revision back.

What shipped on 1 September

  • Publish agent-built plugins and shaders to the Figma Community, or privately to an Organization or Enterprise workspace.
  • Animated and interactive shaders: motion and mouse reactivity, not only a static fill or effect.
  • Code access: view and download the source so a third-party agent can edit it.
  • MCP updates: list, read, create, and update generative plugins and shaders from an agent that implements the Figma MCP server.

Figma’s developer docs make the write path explicit. `create_shader` and `update_shader` require the `figma-shaders` skill. Plugin writes require `figma-generative-plugins`. Those skills are prerequisites, not optional flavor. A successful update is built, versioned, and deployed as part of the call.

Who can use the agent, and when credits start

King’s post says anyone with access to the Figma design agent can build generative plugins and shaders. The agent is in open beta for Full seats on all plans. Collab, Dev, and View seats can use it in drafts. It is free during beta and will start consuming AI credits in a few weeks. If you are budgeting Figma AI, treat “free beta” as a date, not a plan.

  1. Confirm which seats in your org have the design agent, and whether drafts-only access is enough for the people who will actually build shaders.
  2. Decide whether publishing is Community, org-private, or neither. Org publishing is Organization and Enterprise.
  3. If engineers will edit the output, require the Figma MCP server in the same agent you already trust for code, and load the official skills before the first write.
  4. Ask who can revert a bad `update_shader` the same way you would revert a plugin. Versioning is not the same as an approval gate.

Where this sits on a Bookmarkit shortlist

Keep Figma as the design system of record. Add Claude Code or Cursor when the shader or plugin leaves the canvas. If the team is already on Gemini, Google Antigravity is the other agent surface to test against the same MCP file. For the protocol risk behind any MCP server, read MCP tool poisoning.