Skip to main content
Solved

MCP extension stops responding after Claude Desktop update — protocol version mismatch

  • April 15, 2026
  • 9 replies
  • 276 views
Andrei Carvalho
After updating Claude Desktop to the latest version (April 14, 2026), the Figma MCP extension (v1.0.4) starts successfully but never responds to tool calls. The server initializes, lists tools, and then times out on every subsequent request. The root cause, identified in the MCP logs, is a protocol version mismatch: Claude Desktop now negotiates 2025-11-25, while the Figma extension responds with 2025-06-18.MCP server logs✓ Server started and connected successfully✓ Client → initialize  { protocolVersion: "2025-11-25" }   ← Claude Desktop✓ Server → initialize  { protocolVersion: "2025-06-18" }   ← Figma extension✓ tools/list → OK (get_design_context, get_metadata, etc.)✗ Any tool call → no response / timeout after 4 min✗ Client transport closed (intentional shutdown)

The pattern repeats on every session restart, reinstall of the extension, and reboot of Claude Desktop. Protocol negotiation succeeds but tool execution never reaches the extension.r

Best answer by Stephen Kung

I found out the issue: I had the unlabelled Figma (desktop) connector for claude installed as well as the Figma (remote) connector and they caused a conflict. I just uninstalled the desktop connector. There wasn’t a clear label on which was which 

    9 replies

    J
    Figmate
    • Junko3
    • Figmate
    • April 17, 2026

    Hi ​@Andrei Carvalho, 

     

    Thanks for the detailed report!

    It sounds like every tool call is timing out after 4 minutes when using the Figma MCP server with Claude Desktop, and the logs are pointing to a protocol version mismatch between the two (`2025-11-25` on the Claude Desktop side vs `2025-06-18` on the Figma extension side). I'll go ahed and flagged to our team for a review.

     

    One quick thing before I do, could you confirm whether you're using the Desktop MCP Server?That'll help us track down the right place to investigate.

    I'll follow up here as soon as I hear back.

     

    Thanks!

    Stephen Kung
    • Stephen Kung
    • New Participant
    • April 17, 2026

    I’m having this problem too, but I don’t know how to troubleshoot it. It is saying the same thing. Timing out after four minutes. Saying that the sigma MCP server may have dropped or stalled

    Stephen Kung
    • Stephen Kung
    • New Participant
    • April 17, 2026

    I’m using Claude desktop for Mac and figma desktop

    J
    Figmate
    • Junko3
    • Figmate
    • April 17, 2026

    Thanks for following up!
    I've gone ahead and passed this post to our team. I’ll update once I hear back.

    Stephen Kung
    • Stephen Kung
    • New Participant
    • April 17, 2026

    It’s working again on my end fyi

      mariosux
      • mariosux
      • New Member
      • April 17, 2026

      I’m having the same issue, can’t use mcp in the last week. I’m using Claude, says the connection is up and running, requests is made by claude, but then returns a time out error. (Claude specifically says it sees the love connection, then starts the request get_design_context, and then says its times out)

      I’m using Figma desktop app, and claude app (windows laptop). I’ve also tried mcp using browser for both figma and claude, and its the same issue. I’ve used mcp before and it worked, it stopped working recently.

       

      I tried restarting apps, disabling mcp and enabling again, being active in dev mode in figma, and selecting node whist mcp connection is called. nothing worked so far. I’d appreciate any help, maybe a bug that needs to be addressed by figma.

       

      looking forward to an update by Junko3. It’s very time intensive not being able utilise mcp

        Stephen Kung
        • Stephen Kung
        • New Participant
        • April 20, 2026

        ​@Junko3 Actually sorry, I’m using it today and it’s gone back to not working now…

        No result received from the Claude Desktop app after waiting 4 minutes. The local MCP server providing this tool may be unresponsive, crashed, or not running. Further calls to this tool are likely to time out the same way; consider using an alternative approach or ask the user to restart their local MCP servers.

        Stephen Kung
        • Stephen Kung
        • New Participant
        • April 20, 2026

        ​@Junko3 specifically it’s not working on my work MacBook Pro but it works if I request access to the figma node url via my iPhone Claude app.

        Stephen Kung
        • Stephen Kung
        • New Participant
        • Answer
        • April 21, 2026

        I found out the issue: I had the unlabelled Figma (desktop) connector for claude installed as well as the Figma (remote) connector and they caused a conflict. I just uninstalled the desktop connector. There wasn’t a clear label on which was which 

        Terms & ConditionsAccessibility statement