Hey, this is a known issue with remote OAuth-based MCP servers. The connection fails during OAuth discovery when the MCP client builds a derived URL that doesn’t pass validation, even though your https://mcp.figma.com/mcp config URL itself is fine. The same symptom has been reported for Stitch and a few other remote MCP servers, so it’s not Figma-specific.
The issue is tracked internally and being looked at. No ETA on a fix yet. I’ll post here when there’s an update.
Workaround for now: stick with the local Figma MCP that you already have working, http://127.0.0.1:3845/mcp via the Figma desktop app’s Dev Mode MCP. It covers most of the tooling. The remote endpoint won’t work reliably until the OAuth flow is fixed on our side.
Related threads with the same root cause if you want to follow along: