How to connect Codex to Figma, and fix read-only access

By Sabarish Sanjay, maker of Crossfade · Updated 7 November 2026

Codex can create and change real layers in Figma, but one setup mistake leaves it stuck on read-only. Here's how to connect it, and how to fix that.

Set up in the Codex app

1. In the upper-left corner of the Codex app, click Plugins.
2. Click + next to Figma, then Install Figma.
3. Click Allow access when asked.
4. Go back to Codex. The plugin shows as connected.

Set up in the Codex CLI

The CLI route adds the remote server, without Figma's skills:

codex mcp add figma --url https://mcp.figma.com/mcp

Authenticate when prompted, then restart Codex.

Fix: “I only have read-only access”

This comes up a lot. In one forum thread, reinstalling didn't help, and neither did turning on the desktop server. The fix that worked was adding the remote server with the command above and restarting.

The reason is simple. Figma has two servers, and the desktop one can't write:

If it's still read-only, check the seat. Figma's docs say writing outside your drafts needs a Full seat, and you need edit access to the file.

Another route: a local plugin

A plugin in your open file skips both servers, so there's no seat requirement beyond edit access and no call limits. Crossfade, which I make, offers Codex in its setup screen.

To be straight with you: Crossfade is built and tested on Claude Code. Codex connects through the same local server, but it hasn't been fully tested yet. If that matters for your work, see the free alternatives too. TalkToFigma lists Codex support.

Common questions

Why does Codex say it only has read-only access to Figma?

The most common cause reported on Figma's forum is that Codex is connected to the desktop server, which can't write. Adding the remote server fixed it for those users.

Can Codex write to Figma on any seat?

Through Figma's server, writing outside your drafts needs a Full seat and edit access to the file.