PlugWiki
Figma MCP Server logo

Add Figma to OpenAI Codex

Install Figma from the Codex app's Plugins panel or add it in the CLI, sign in with Figma, and Codex can turn your designs into code.

Install Figma from the Plugins panel in the Codex app, or add it with the CLI command above, then sign in with your Figma account. Codex can then read the frame you link in your prompt and write code that matches it. The CLI, the IDE extension and the Codex app share one config file, so one setup covers all three. Sign-in is the weak spot on Windows, where several open reports show it failing.

Good for

  • Developers who use Codex to build UI from Figma frames
  • People who move between the Codex app, the CLI and the IDE extension
  • Teams in managed Codex workspaces whose admins approve plugins
  • Anyone who only needs to read designs, through the read-only desktop server

Add Figma to OpenAI Codex

Codex

  1. 1

    Open the Codex app and click Plugins in the upper left.

  2. 2

    Click + next to Figma, then Install Figma.

  3. 3

    Click Allow access in the browser. Figma then shows as connected.

Requires Figma account.

Read-only mode: Use the desktop server option: Figma says it cannot write to the canvas. On the hosted server, add default_tools_approval_mode = "writes" under [mcp_servers.figma] so Codex asks before any tool that can make changes.

The app plugin adds Figma's skills; the CLI and config file options give the plain connection. After codex mcp add, Codex asks you to sign in to Figma; to sign in again later, run codex mcp login figma. The CLI, IDE extension and Codex app share ~/.codex/config.toml, so one setup covers all three. In a managed workspace your Codex admin must allow third-party plugins and approve the Figma tools.

From the vendor's docs. Source.

Common errors and fixes

  • 'OAuth token exchange failed: Client ID is required' after browser sign-in

    Cause: Open Codex CLI bug on Windows; the same account signs in from other apps.

    Fix: No fix yet; the report is open.

    codex Source

  • 'OAuth state not found' and the app stays on 'Finish connecting Figma in your browser'

    Cause: Open Codex Windows app bug.

    Fix: No fix yet; signing out and back in did not help the reporter.

    codex Source

  • Figma tools vanish from every thread after the app reconnects

    Cause: In one Windows report, a reinstall left the Figma entry in config.toml set to enabled = false.

    Fix: Set it back to enabled = true in ~/.codex/config.toml and reload your threads.

    codex Source

  • codex mcp login figma fails with 'invalid_redirect_uri'

    Cause: Codex's sign-in callback did not match what Figma accepted.

    Fix: Update Codex and retry; a user reported Figma fixed it in June 2026.

    codex Source

  • Figma plugin shows 'App Unavailable'

    Cause: One user traced it to Codex failing to download its curated plugin catalog; others said the same fix worked.

    Fix: A user copied the Figma plugin into ~/.codex/plugins/cache/openai-curated/figma and set [plugins."figma@openai-curated"] enabled = true.

    codex Source

  • Figma plugin or some tools missing in a managed workspace

    Cause: Your admin has not allowed third-party plugins or approved the Figma tools.

    Fix: Ask your Codex admin to allow third-party plugins and approve the Figma tools.

    codex Source

  • Codex keeps signing in to the old Figma account

    Cause: Codex reuses the stored Figma login.

    Fix: Run codex mcp logout figma, then codex mcp login figma and sign in with the other account.

    codex Source

Permissions

Medium risk

Through the hosted server Codex can create and change content in any Figma file you can edit. Make Codex ask before tools that change things, or use the read-only desktop server if you only need to read designs.

What it can do

Watch out for

  • It can change your Figma files

    Through the hosted server Codex can create and edit content in files you can edit. Set the Figma server to ask before writes so you approve each change. learn.chatgpt.com

  • You can switch off Figma tools you do not want

    Codex lets you allow or block single tools for a server, so you can keep the read tools and drop the ones that write. learn.chatgpt.com

  • Admins control plugins in managed workspaces

    In a managed workspace the Figma plugin and its tools appear only if your admin allows third-party plugins and approves the Figma tools. developers.figma.com

  • Signing out takes more than closing Codex

    Codex keeps your Figma login between sessions. Run codex mcp logout figma to remove it. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyAdd the desktop server in Codex Settings > MCP servers (http://127.0.0.1:3845/mcp); Figma says it cannot write to the canvas. On the hosted server, set default_tools_approval_mode = "writes" under [mcp_servers.figma] so Codex asks before tools not marked read-only, or list the write tools in disabled_tools.
Talks tomcp.figma.com (HTTPS). 127.0.0.1:3845 (desktop server, local only)
Sign-in and keysCodex keeps the Figma sign-in between sessions; codex mcp logout figma removes it.
Scopes

  • Figma files your account can open; edits only in files you can edit

Works in

Tap an app to see how to set it up and any known problems.

Questions

Why does Figma not show up in Codex?

In a managed workspace, your Codex admin has to allow third-party plugins and approve the Figma tools first. On Windows, users also report Figma tools vanishing after the app reconnects.

How do I add Figma to Codex?

In the Codex app, click Plugins, click + next to Figma, then Install Figma and Allow access. In the terminal, use the Codex CLI option in the install box and sign in when asked.

How do I sign in to Figma again from the Codex CLI?

Run codex mcp login figma. Codex opens the Figma sign-in in your browser and saves the new login.

Sign-in fails with 'Client ID is required'. Is there a fix?

Not yet. It was reported on the Codex CLI on Windows in October 2026 and is still open; the same Figma account signed in fine from Claude Code.

codex mcp login figma fails with invalid_redirect_uri. What now?

Update Codex and try again. A user reported in June 2026 that Figma had fixed it and sign-in worked on the latest Codex.

The Figma plugin says 'App Unavailable' in the Codex app. Why?

One user traced it to Codex failing to download its plugin catalog. They fixed it by copying Figma's plugin into Codex's plugin folder by hand and turning it on in config.toml.

Figma tools disappeared from my Codex threads. How do I get them back?

Open ~/.codex/config.toml and check the Figma entry. One Windows user found it switched to enabled = false after a reinstall; setting it back to true and reloading threads brought the tools back.

How do I switch to another Figma account in Codex?

Run codex mcp logout figma to remove the stored login, then codex mcp login figma and sign in with the other account.

Can I use the Figma desktop server with Codex?

Yes. Use the desktop server option in the install box to add it under Codex Settings > MCP servers. It is read only and needs the Figma app open with the server on.

Figma calls time out in Codex. Can I give them longer?

Yes. Codex stops a tool call after 60 seconds by default; raise tool_timeout_sec under [mcp_servers.figma] in config.toml.

Information

updated Nov 1, 2026

WebsiteDocsGitHubOfficial MCP RegistryPricingLink

More on this

Sources

Docs, issue trackers and discussions this page is built from.

Show all 11
  1. developers.figma.com · developers.figma.com
  2. developers.figma.com · developers.figma.com
  3. learn.chatgpt.com · learn.chatgpt.com
  4. developers.figma.com · developers.figma.com
  5. github.com · github.com
  6. github.com · github.com
  7. github.com · github.com
  8. github.com · github.com
  9. github.com · github.com
  10. Codex CLI mcp subcommands (source) · github.com
  11. github.com · github.com

Updated Nov 1, 2026.