Failed to set up figma remote mcp server in cursor

Support Bug Reports
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.