VS Code + Figma MCP Failing to Create Authentication Token

Hi ​@Lmasniuk, thanks so much for taking the time to put together such a detailed write-up and for outlining all the troubleshooting steps you’ve already tried - really appreciate the thorough context here.

I’m currently checking in with the team on this to see whether this is a known issue or if there’s any additional guidance we can share. I’ll get back to you as soon as I have more information.

Thanks again for your patience in the meantime!

Update: I’ve went ahead to create a support ticket for you, your ticket number is #1939030.

I have this exactly same problem. I noticed it first time early this week.

I have same same setup, VS Code + Figma MCP ( https://mcp.figma.com/mcp) in my config, and it behaves exactly same way.
 

If I however use copilot from cli, it seems to be working as expected. Copilot CLI has that same MCP with same url, and it behaves just fine.

Hi ​@Joonas Hämäläinen, thanks for confirming you're seeing the same behavior and for sharing the additional detail about Copilot CLI.

From what you've described, the Figma MCP connection fails when authenticating through VS Code using the https://mcp.figma.com/mcp endpoint, while the same MCP server and URL work as expected through Copilot CLI. That comparison is really helpful for narrowing down the issue.

I've gone ahead and created a support ticket for you so the team can investigate this further. Your ticket number is #1939034.

Someone from the team will be reaching out shortly, so please keep an eye on your inbox. Thanks again for taking the time to flag this.

​@Celyn_L I have the same problem. Can you help mee about or tell me how i can fix?

Tnks!

Hi ​@Marcus_Paula, thanks for chiming in. I'm sorry to hear you're running into the same issue.

I've gone ahead and created a support ticket for you so the team can take a closer look. Your ticket number is #1952961.

It would be great if you could reply directly to the ticket with a few more details about your setup, including how you've configured the MCP integration and any error messages you're seeing. This will help the team investigate more efficiently.

Someone from the team will be in touch with next steps shortly. Thanks for your patience in the meantime 🙏

Are there any new updates on this problem ? i got the same issue over weeks now.  Thanks! 

Hey ​@Dennis Piotrowski, thanks for chiming in, and I'm sorry to hear you've been experiencing the same issue.

We've been able to identify what's causing this. That said, because of the nature of the issue, it's likely going to take the team a little while to put together a fix.

I don't have an ETA to share at the moment, but I've passed your report along to our Product and Engineering teams so they have visibility into the impact this is having. We'll be sure to post an update here as soon as there's any news to share, including when the fix is available.

Thanks so much for bearing with us in the meantime! 🙏

I got the same issue too.

I installed figma MCP from the VS code extensions, and here is the figma MCP config:

```

"com.figma.mcp/mcp": {

  "type": "http",

  "url": "https://mcp.figma.com/mcp",

  "gallery": "https://api.mcp.github.com",

  "version": "1.0.3"

}

```

When I click the Start Server, and a browser window was opened, I clicked the Agree & Allow Access.

It says sign-in successful, but when back to VS code, it says no,

I tried yes, but still not work.

Below is the MCP’s output when start it:

```

2026-06-30 09:43:47.367 [info] Starting server com.figma.mcp/mcp

2026-06-30 09:43:47.367 [info] Connection state: Starting

2026-06-30 09:43:47.368 [info] Starting server from LocalProcess extension host

2026-06-30 09:43:47.368 [info] Connection state: Running

2026-06-30 09:43:49.612 [info] Discovered resource metadata at https://mcp.figma.com/.well-known/oauth-protected-resource

2026-06-30 09:43:49.612 [info] Using auth server metadata url: https://api.figma.com

2026-06-30 09:43:50.942 [info] Discovered authorization server metadata at https://api.figma.com/.well-known/oauth-authorization-server

2026-06-30 09:43:52.382 [info] Waiting for server to respond to `initialize` request...

2026-06-30 09:43:57.370 [info] Waiting for server to respond to `initialize` request...

2026-06-30 09:44:02.369 [info] Waiting for server to respond to `initialize` request...

2026-06-30 09:44:07.371 [info] Waiting for server to respond to `initialize` request...

2026-06-30 09:44:12.370 [info] Waiting for server to respond to `initialize` request...

2026-06-30 09:44:17.371 [info] Waiting for server to respond to `initialize` request...

2026-06-30 09:44:22.371 [info] Waiting for server to respond to `initialize` request...

2026-06-30 09:44:25.312 [warning] Error getting token from server metadata: Error: Failed to create authentication token

2026-06-30 09:44:25.325 [info] Connection state: Error 401 status sending message to https://mcp.figma.com/mcp: Unauthorized

```

And below is the Auth log of Figma MCP

```

2026-06-30 09:43:50.945 [info] Getting sessions for scopes: all

2026-06-30 09:43:50.945 [info] Getting sessions for scopes: all

2026-06-30 09:43:50.945 [info] Getting sessions for scopes: all

2026-06-30 09:43:50.945 [info] Getting sessions for scopes: mcp:connect

2026-06-30 09:43:50.945 [info] Found 0 sessions for scopes: mcp:connect

2026-06-30 09:43:52.384 [info] Creating session for scopes: mcp:connect

2026-06-30 09:43:52.389 [info] Opening authorization URL for scopes: mcp:connect

2026-06-30 09:44:00.704 [info] Authorization code received for scopes: mcp:connect

2026-06-30 09:44:00.704 [info] Exchanging authorization code for token...

2026-06-30 09:44:14.617 [error] Failed to create token via flow 'URL Handler': Error: Token exchange failed: 400 Bad Request - {"error":"Client secret is required","error_description":"An error occurred processing your request"}

2026-06-30 09:44:14.623 [info] Opening authorization URL for scopes: mcp:connect

2026-06-30 09:44:24.075 [info] Authorization code received for scopes: mcp:connect

2026-06-30 09:44:24.076 [info] Exchanging authorization code for token…

```

Hi ​@Mafee Wu, thanks for chiming in and for sharing your logs - the details you've provided are really helpful.

I've passed your report, along with the logs, to our Engineering team to help with their investigation. I'll post back here as soon as I hear anything from the team.

Really appreciate your patience in the meantime, and thanks again for taking the time to include the logs 🙏

Exact same problem

For anyone coming to this post now; the team responded to me indicating that this is a known issue and there is no fix for it currently.

I'm experiencing exactly the same issue.

Environment:

• VS Code 1.122.1 (Stable)

• macOS Sequoia (Apple Silicon)

• Official Figma MCP server (https://mcp.figma.com/mcp)

What happens:

1. I start the Figma MCP server in VS Code.

2. VS Code opens the browser for OAuth authentication.

3. I click "Agree & Allow Access" in Figma.

4. The browser redirects back to VS Code.

5. VS Code says that authentication has not been completed and asks me to try another method.

6. If I retry, the authentication ultimately fails with:

Failed to create authentication token
401 Unauthorized

The MCP log shows:

Discovered resource metadata at https://mcp.figma.com/.well-known/oauth-protected-resource
Using auth server metadata url: https://api.figma.com
Discovered authorization server metadata at https://api.figma.com/.well-known/oauth-authorization-server
Waiting for server to respond to `initialize` request...
...
Failed to create authentication token
401 Unauthorized

I have already verified the following:

• My Figma account is working correctly.

• My Personal Access Token is valid (GET https://api.figma.com/v1/me returns 200 OK when using the X-Figma-Token header).

• The mcp.json configuration is the standard one recommended in the documentation.

• I have already tried reauthorizing, restarting VS Code, and using a different browser.

This was working previously and then suddenly stopped without any configuration changes.

Please let me know if there is any workaround or if you need additional logs to help diagnose the issue.