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!
