Add figma mcp meet 400 error

Open 💬 8 comments Opened May 21, 2026 by zehao365

What version of Codex CLI is running?

0.132.0

What subscription do you have?

max

Which model were you using?

_No response_

What platform is your computer?

_No response_

What terminal emulator and version are you using (if applicable)?

windows powershell

Codex doctor report

What issue are you seeing?

codex mcp add figma --url https://mcp.figma.com/mcp
Added global MCP server 'figma'.
Detected OAuth support. Starting OAuth flow…
Error: Registration failed: Dynamic registration failed: Registration failed: HTTP 400 Bad Request: {"error":"invalid_redirect_uri"}

What steps can reproduce the bug?

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

What is the expected behavior?

_No response_

Additional information

back to 0.129.0 -- execute success

View original on GitHub ↗

8 Comments

weilliao05621 · 1 month ago

hi @zehao365, having same issue brings me here.

for me, i install the codex app (the desktop version) to install figma plugin to pass OAuth. After that process, I back to use CLI.
hope this work-around can help you to use figma mcp in CLI for now

lushevol · 1 month ago

The same issue with me

richardWebdezign · 1 month ago

Posting on behalf of codex:

I ran into the same issue with the Figma MCP login flow on Codex CLI 0.133.0. After debugging locally, the problem appears to be the redirect URI shape generated by Codex during OAuth. Codex generates: ``text http://127.0.0.1:<port>/callback/<callback-id> ` but Figma appears to only accept: `text http://127.0.0.1:<port>/callback ` I tested a local compatibility patch that retries the OAuth flow without the appended callback ID after receiving invalid_redirect_uri`, and login succeeded immediately afterward. This seems provider-specific rather than a generic OAuth failure, since the existing callback format may still be valid for other MCP providers. A fallback/retry strategy might therefore be safer than changing the default redirect format globally.

Norman-GM · 1 month ago

same issue, even reinstall several times still can't fix it

ruolis · 1 month ago

I have encountered the same problem, what should I do?

zehao365 · 1 month ago

Try downgrading to version 0.129.0 first to complete the Figma MCP authentication, then upgrade back to the latest version. This should fix the issue.

benekuehn · 1 month ago

Downgrading works, less destructive and also works: npx -y @openai/codex@0.129.0 mcp login figma

jfedor · 1 month ago

Figma has fixed this, and I was able to auth using latest codex with no issues