Failed to set up figma remote mcp server in cursor

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have tried to delete cursor cache ,restart cursror and delete figma mcp and reinstall figma mcp , it still can’t load the mcp tool , end up in error output .
the json is ( which works perfectly in vscode) :
“Figma”: {
“url”: “https://mcp.figma.com/mcp”,
“headers”: {}
}

the error output is :
2026-04-08 21:10:49.435 [info] [V2] Handling CreateClient action
2026-04-08 21:10:49.435 [info] [V2 FSM] connection:connect_start: conn=idle,auth=unknown → conn=connecting,auth=unknown
2026-04-08 21:10:50.606 [info] Using OAuth scopes: mcp:connect
2026-04-08 21:10:53.061 [warning] Transient error connecting to streamableHttp server: Invalid URL protocol: the URL must start with http: or https:.
2026-04-08 21:10:53.067 [warning] Connection failed: Invalid URL protocol: the URL must start with http: or https:.
2026-04-08 21:10:53.067 [warning] [V2 FSM] connection:connect_failure: conn=connecting,auth=unknown → conn=failed,auth=unknown
2026-04-08 21:10:53.067 [info] CreateClient completed, connected: false, statusType: error

Steps to Reproduce

  1. open cursor
  2. add figma mcp in the mcp config json file
    “Figma”: {
    “url”: “https://mcp.figma.com/mcp”,
    “headers”: {}
    }
  3. save it and then it’s status color always show red . and never load those tools , so it failed to set up the figma mcp server at the begining

Expected Behavior

the figma mcp server tools should be loaded successfully and then start to open the browser to process authorization…

Operating System

MacOS

Version Information

Version: 3.0.12 (Universal)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z (4 days ago)
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.1.0

Does this stop you from using Cursor

Yes - Cursor is unusable

4

Hey, this is a known issue with remote MCP servers in Cursor. It affects not only Figma, but also Stitch, Vercel, and other endpoints. The error happens because when the MCP client connects, it tries to do OAuth discovery, and during that it builds an incorrect internal URL, even if your original https:// URL is valid.

For now, the best workaround is to use the local Figma MCP instead of a remote URL:

{
  "mcpServers": {
    "Figma": {
      "command": "npx",
      "args": ["-y", "figma-developer-mcp", "--stdio"],
      "env": {
        "FIGMA_API_KEY": "your-figma-api-key"
      }
    }
  }
}

You can generate an API key in Figma: Settings > Security > Personal access tokens.

The team is aware of this issue. There’s no timeline yet, but your report helps us prioritize it. Let me know if the local setup works.

7

thanks , this version works perfectly!

1 Like
8

This version works successfully, but it has only two tools. How can I use other tools listed in this link: https://developers.figma.com/docs/figma-mcp-server/tools-and-prompts/, including tools like use_figma that are essential for design workflow? Thank you.

截屏2026-04-09 14.22.32
截屏2026-04-09 14.22.32838×266 28 KB

11

Yes, this is expected behavior. The npm package figma-developer-mcp is a community project with a limited set of tools. The full toolset, including use_figma and other tools from Tools and prompts | Developer Docs, is only available through the remote MCP server https://mcp.figma.com/mcp.

Unfortunately, connecting to remote MCP servers with OAuth doesn’t work in Cursor right now. That’s the same bug from that thread. The team is aware, but there’s no ETA yet.

For now, using the local figma-developer-mcp setup is the only working workaround, but it has limited functionality. Sorry for the inconvenience.