[Bug] MCP Server stuck in infinite "Invalid URL protocol" retry loop despite removing all configs

Support Bug Reports
,
15

Hey, I can see in the logs that after clearing the cache, the “Invalid URL protocol” error is still showing up. That means the config is being recreated from another source. Also, there are now Connect Timeout errors on the SSE fallback.

A couple questions:

  1. In your mcp.json (project or global), do you still have the Figma MCP set as "url": "https://mcp.figma.com/mcp"? If yes, this is a known issue with remote MCP servers in Cursor 3.x where OAuth discovery builds an incorrect internal URL.

  2. What Cursor version are you on right now? In another thread I see 3.0.12.

If you still need Figma MCP, the best workaround right now is to use the local version instead of the remote URL. I already wrote more details in your other thread Failed to set up figma remote mcp server in cursor - #4 by deanrie, but I’ll paste it here too:

{
  "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 the issue. There’s no ETA yet, but reports help prioritize it. Let me know if the local setup worked for you.