Skip to main content
Lmasniuk
New Member
May 27, 2026 9:48 PM UTC
Solved

VS Code + Figma MCP Failing to Create Authentication Token

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!

Celyn_L
Celyn_LSolution
Figmate
Aug 4, 2026 8:45 AM UTC

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:

  1. VS Code sends an initialize request to the Figma MCP server.
  2. The Figma MCP server returns a 401 response with information on how to authenticate.
  3. 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 🙏

36 replies

MiguelCanelo
New Member
Sep 8, 2026 7:15 AM UTC

(8 September 2026: This post has been merged into a similar thread by a moderator to keep the discussion in one place.)

Hi!

For approximately over a month now, I have been experiencing connection issues between Visual Studio Code and Figma via MCP.

It used to work perfectly, but suddenly I was no longer able to establish a connection. When starting the MCP server, Visual Studio Code gives me the following response:
 

2026-09-08 09:06:34.389 [info] Connection status: Running

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

2026-09-08 09:06:35.049 [info] Using auth server metadata URL: https://api.figma.com

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

2026-09-08 09:06:39.391 [info] Waiting for server to respond to initialize request...

2026-09-08 09:06:44.391 [info] Waiting for server to respond to initialize request...

2026-09-08 09:06:48.792 [warning] Error getting token from server metadata: Error: Failed to create authentication token

2026-09-08 09:06:48.793 [info] Connection status: Error 401 status sending message to https://mcp.figma.com/mcp: Unauthorized

 

The error reference I received is: 7d2e4051-a212-4c46-9ecf-c8b3dc36c863

Could you please help me find a solution?

Daria P
New Member
Sep 17, 2026 11:26 AM UTC

Same issue in my work account with a SSO auth!

Carlos_Madrigal
New Member
Sep 17, 2026 6:32 PM UTC

I asked the agent to replay the MCP protocol with the Figma MCP server to identify where it was struggling. I hope this helps.

We’re blocked. Do you have an ETA for the fix?

---

With a valid Figma OAuth token in FIGMA_ACCESS_TOKEN, this reproduces the failure without putting the token in curl’s command-line arguments:

Bash

printf 'header = "Authorization: Bearer %s"\n' "$FIGMA_ACCESS_TOKEN" |
curl --config - --silent --show-error --include --max-time 10 \
https://mcp.figma.com/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-H 'MCP-Protocol-Version: 2026-07-28' \
-H 'Mcp-Method: subscriptions/listen' \
--data '{
"jsonrpc":"2.0",
"id":4,
"method":"subscriptions/listen",
"params":{
"_meta":{
"io.modelcontextprotocol/protocolVersion":"2026-07-28",
"io.modelcontextprotocol/clientInfo":{
"name":"curl-mcp-diagnostic","version":"1.0.0"
},
"io.modelcontextprotocol/clientCapabilities":{}
},
"notifications":{
"toolsListChanged":true,
"promptsListChanged":true,
"resourcesListChanged":true
}
}
}'

Fix direction: Figma needs working modern subscriptions or corrected capability advertising. Client-side, tolerating unavailable subscriptions or using legacy 2025-11-25 is a potential workaround; the legacy discovery path passed. No configuration was changed.

Jaycee Lewis
Figmate
Figmate
Sep 18, 2026 11:02 PM UTC

Hey ​@Carlos_Madrigal Thanks for flagging this. I opened a support ticket for this. The ID is 2141055 and the email subject line is VS Code + Figma MCP Failing to Create Authentication Token. Please keep an eye on your email (and spam folder if necessary) for the email and any replies from our team. Thank you! — Jaycee

Bianca CONDRUZ
New Member
Sep 28, 2026 11:41 AM UTC

I have the same issue

Zlatko123
New Member
Oct 7, 2026 1:13 PM UTC

same issue, solved it by removing the stored credentials. execute this command in VSC:
 

select Figma and then OK, restart VSC and the auth should work after starting the mcp

Bianca CONDRUZ
New Member
Oct 8, 2026 2:04 PM UTC

Thank you! It worked!

Jackson Zhang
New Member
Oct 15, 2026 8:05 AM UTC

I have same question,when i want to initiate figma mcp server A pop-up appeared, asking me to add client registration details.(Quth Client)It won't start up properly; what should I do?

adamsmasher
Figmate
Figmate
Oct 15, 2026 9:53 PM UTC

Thanks for the reply, ​@Jackson Zhang! Could you share which app and version you’re connecting from, and whether you’re using its built-in MCP support or an extension?

 

A screenshot of the client-registration popup, the Figma server URL you configured, and any error text would also help narrow this down. Make sure you hide any tokens or secrets in your screenshots or text, though.

Jackson Zhang
New Member
Oct 16, 2026 2:36 AM UTC

Hi , I was using the latest version of VS Code,I was going through the standard MCP server installation process when a "Dynamic client registration not supported" error popped up, immediately followed by a window prompting me to provide client registration details. I’ve tried uninstalling and reinstalling multiple times, but I can’t find a solution—I’m stuck at the initial authentication step.

LyesLEK
New Member
Oct 23, 2026 11:39 AM UTC

Hello, i have the same problem : The browser opens, I authenticate, I grant access to the MCP—everything goes well, but there is an issue in the token processing workflow.

 

2026-10-23 13:22:07.256 [info] Opening authorization URL for scopes: mcp:connect

2026-10-23 13:22:12.245 [info] Authorization code received for scopes: mcp:connect

2026-10-23 13:22:12.245 [info] Exchanging authorization code for token...

2026-10-23 13:22:21.033 [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"}

adamsmasher
Figmate
Figmate
Oct 24, 2026 3:50 PM UTC

Thanks for your reply, ​@LyesLEK, and for including log info - they show that the authorization code comes back, but the next step fails when it’s exchanged for a token. 

 

Could you share your client and version, OS, and how you added the Figma MCP connection - for example, through an extension or manually? It would also help to know whether this previously worked and whether you’re running locally or through something like WSL or SSH. Thanks!

LyesLEK
New Member
Nov 16, 2026 11:25 AM UTC

Hello ​@adamsmasher 

Thanks for your reply 

 

Client : Visual Studio Code 

 

OS : Windows 11 Entreprise (Build : 26200.9911)

 How you added the Figma MCP connection : 

I’ve tried a few different approaches; the main one is as follows:

I am logged into our Figma environment for our project. In the MCP section on the right, I click the "+" icon and select VS Code. 


This automatically opens VS Code so I can add the extension. Once I’ve added the extension, I attempt to initiate the MCP connection, and a window appears asking for authorization.

Sur GitHub Copilot : The MCP works well. I am specifically looking for the Figma extension (+Add Server). Then a window appears asking for authorization; I agree => Connection OK.

 

Thanks

Shola Ogunde
New Member
Nov 16, 2026 3:57 AM UTC

Potential Workaround

I had a similar issue using Figma MCP with Codex Desktop and ChatGPT helped me troubleshoot it.

Workaround for Norton 360 Premium

Open Norton 360
1. Select Security.
2. Navigate to Advanced Security → Web → Safe Web.
3. Open the Settings tab.
4. Expand Safe Web dropdown
5. Look for HTTPS scanning.

If HTTPS scanning is set
1. Open the Exclusions tab.
2. Add these sites

  • mcp.figma.com : for MCP communication
  • api.figma.com : for OAuth metadata and token operations
  • www.figma.com : for interactive authorisation

Adding one server is not enough. All related endpoints need to be added. I got ChatGPT to help me discover which endpoints were used as part of the process - using the following standard commands

  • curl.exe -sS -i --max-time 20 "https://mcp.figma.com/.well-known/oauth-protected-resource/mcp"
  • curl.exe -sS -i --max-time 20 "https://mcp.figma.com/.well-known/oauth-authorization-server"