New Member

Solved

VS Code + Figma MCP Failing to Create Authentication Token

Forum|Forum|3 months ago
May 27, 2026
24 replies
1584 views

Hi Figma team and community,

I am trying to use Figma MCP (Model Context Protocol) integration in VS Code, but I’m running into a persistent authentication token creation issue that prevents the connection from working.

Problem Description

When I configure mcp.json like this:

"figma": {"type": "http","url": "https://mcp.figma.com/mcp"},

and start the server in VS Code, a browser opens to https://www.figma.com/oauth/mcp /... where I click “Agree and Allow Access”.

It seems that fails then a window in VS Code shows “You have not yet finished authenticating to 'Figma MCP'. Would you like to try a different way? (URL Handler)”, which I click “yes” and it takes me through the same Figma OAuth Access flow in the browser, and re-opens VS Code.

After doing this, the Figma MCP server fails to start and I see the following MCP Output Error messages:

[warning] Error getting token from server metadata: Error: Failed to create authentication token

[info] Connection state: Error 401 status sending message to https://mcp.figma.com/mcp: Unauthorized

As far as I can tell, Figma + VS Code are failing to create an authentication token and no Figma MCP account in VS Code is created and logged into.

Workarounds Tried

Tried using the Figma MCP tool from VS Code’s MCP marketplace
Restarted VS Code
Logged out and back in on Figma.com
Removed and re-added "https://www.figma.com" to the trusted domains for VS Code
Ran the VS Code command: “MCP : Reset Trust”
Switching "type": "sse" in mcp.json → does not bypass the validation

Request

Please let me know if this is a known issue or if you have any troubleshooting tips. The Figma MCP connection was working last week but this week it has been failing to authenticate AFAIK.

Additional Info

VS Code version: 1.121.0
OS: macOS 26.3.1
MCP config:

"figma": {"type": "http","url": "https://mcp.figma.com/mcp"},

Impact:

Cannot use Figma Dev Mode + MCP in VS Code
Blocks programmatic access to components, tokens, and design data via MCP

I hope the Figma team can update the metadata to resolve this issue so MCP integration works as intended.

Thank you!

Best answer by Celyn_L

Hi everyone, thanks for chiming in and sharing the additional details.

Just to clarify, the initial 401 Unauthorized response is expected as part of the MCP authentication flow. The flow is:

VS Code sends an initialize request to the Figma MCP server.
The Figma MCP server returns a 401 response with information on how to authenticate.
VS Code then sends the authentication request.

More details here: https://modelcontextprotocol.io/docs/tutorials/security/authorization

@brenelene – Based on the logs you shared, it looks like the authentication flow is being canceled before it completes, rather than the initial 401 response being the root cause. We've also seen reports of inconsistent authentication behavior in VS Code during this stage of the flow.

@MiguelCanelo – Based on the steps you outlined, it looks like the browser authentication completes successfully, but the flow doesn't finish after you're redirected back to VS Code. Just a heads up that the initial 401 response is expected as part of the authentication process.

If you are able to share a screen recording of the full authentication flow (from initiating the MCP connection through to the error), that would be really helpful for comparing the behavior with what we've been seeing.

Thanks again all for taking the time to include the logs, screenshots, and environment details 🙏

Celyn_L

Figmate

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.

Joonas Hämäläinen

New Member

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.

Celyn_L

Figmate

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.

Marcus_Paula

New Member

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

Tnks!

Celyn_L

Figmate

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 🙏

Dennis Piotrowski

New Member

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

Celyn_L

Figmate

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! 🙏

Mafee Wu

New Member

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: 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…

```

Celyn_L

Figmate

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 🙏

Koen_van_Niekerk2

New Participant

Exact same problem

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO