Figma remote MCP fails with “Invalid URL protocol” before OAuth (Cursor 3.3.30, macOS)

Support Bug Reports
,
1

Hi Cursor team,

I’m unable to connect the remote Figma MCP server in Cursor.
The connection fails before OAuth starts.

Environment

  • Cursor Version: 3.3.30 (Stable)

  • VSCode Version: 1.105.1

  • Commit: 3dc559280adc5f931ade8e25c7b85393842acf30

  • Electron: 39.8.1

  • Node: 22.22.1

  • OS: macOS Darwin arm64 22.6.0

Minimal config (~/.cursor/mcp.json)

{

“mcpServers”: {

“figma”: {

“url”: “https://mcp.figma.com/mcp”

}

}

}

Error logs (MCP output)

[V2] Handling CreateClient action

[V2 FSM] connection:connect_start: conn=idle,auth=unknown → conn=connecting,auth=unknown

MCP OAuth provider initialized

MCP HTTP exchange failed

Transient error connecting to streamableHttp server: Invalid URL protocol: the URL must start with `http:` or `https:`.

Connection failed: Invalid URL protocol: the URL must start with `http:` or `https:`.

[V2 FSM] connection:connect_failure: conn=connecting,auth=unknown → conn=failed,auth=unknown

CreateClient completed, connected: false, statusType: error

What I already tried

  • Removed duplicate MCP entries (including figma vs Figma)

  • Used minimal config with only one remote figma server

  • Full Cursor restart (Quit and reopen)

  • Re-auth attempts

  • Also tried adding/removing "type": "http"

Important comparison

  • figma-desktop (http://127.0.0.1:3845/mcp) works

  • Only remote https://mcp.figma.com/mcp fails with the URL protocol error

Could you help confirm whether this is a known issue in Cursor’s streamable HTTP/OAuth handling for remote MCP, and if there is a workaround?

Thanks!

5

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: