Skip to main content

Codex is unable to write to Figma

  • April 1, 2026
  • 3 replies
  • 39 views

Jon De Heus

I’ve been playing around with Codex & today I installed the Figma plugin in order to try out some of the new features & skills such as creating a file, creating a design system, etc. Everything went well, I was able to log into my company Figma account and verify that all the skills were present. However, when I attempted to use some of these skills, I was told that I only had read only access.

After this, I attempted to troubleshoot by quitting out of both Figma and Codex, uninstalling & reinstalling the plugin, turning on dev mode & enabling the local MCP server inside of Figma (I was using the remote server before), but nothing seems to work. Based on what I see in the instructions, it should theoretically work out of the box, so to speak.

Has anybody encountered this problem before, and if so, how did you fix it? Perhaps I’m doing something wrong, or if there’s a flag that needs to be enabled on the administrative side that will let me use these skills? If there isn’t anything that needs to be done from the admin side, has anybody been able to fix this from the user side, or is this a Figma issue?

Any clarification from the community would be quite helpful, thanks!

3 replies

Lev Woonder
  • New Member
  • April 2, 2026

Hi! I'm having the same problem. It looks like Figma removed the `generate_figma_design` function due to some issues and didn't announce it officially anywhere.


Lev Woonder
  • New Member
  • April 2, 2026

I found the problem. I had a local MCP server. Just type “codex mcp add figma --url https://mcp.figma.com/mcp” in Codex. It will start working after you restart.


Jon De Heus
  • Author
  • New Member
  • April 2, 2026

I’ll be honest, I was totally unprepared for this to work, but it did! Thanks so much!

For anybody who’s reading this later on, I use Codex both in the terminal and the app. When I ran the above command, I did it in the terminal, but now it seems to work both in the terminal and the app. I’m not sure why, but it works now. You’ll know it works if an authentication modal pops up talking about how you need to authenticate, and when you press the confirmation button it takes you to a page that talks about authenticating for the remote server.