Figma MCP: get_design_context auto-rejected without user intent

Resolved 💬 3 comments Opened Mar 23, 2026 by adarshgupta-chill Closed Mar 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Bug Report: get_design_context Tool Auto-Rejected in Figma MCP
Claude Code version: 2.1.81

Summary:
The get_design_context tool call is being automatically rejected during Figma design-to-code workflows, even though the user did not
intentionally deny it. The get_screenshot tool (called in the same session) works perfectly fine.

Environment:

  • Tool: Claude Code (CLI)
  • MCP Server: Figma MCP (official, via claude.ai Figma integration)
  • Platform: macOS (Darwin 25.2.0)

Steps to Reproduce:

  1. Open Claude Code
  2. Share a Figma URL (e.g. https://www.figma.com/design/zaC36gY3xA1gRhylEpGj9H/...?node-id=2194-7048)
  3. Claude calls get_screenshot → works fine, returns image
  4. Claude calls get_design_context → auto-rejected with error: "The user doesn't want to proceed with this tool use. The tool use was

rejected"

  1. Retrying get_design_context results in the same rejection
  2. User did not manually deny the tool — the rejection happens automatically

Proof from this session:

  • get_screenshot succeeded twice (node 2226:5110 and 2194:7048)
  • get_design_context failed twice (nodes 2226:5110 and 2194:7048) with the same rejection message
  • On the 3rd attempt (after user explicitly said "resume"), get_design_context succeeded — confirming the tool itself works, but the permission prompt is behaving inconsistently (This is according to claude not the user/me)

Expected behavior: Both tools should prompt for approval equally, or be auto-approved if permissions are set.

Actual behavior: get_design_context is silently rejected without user intent.

What Should Happen?

Expected behavior: Both tools should prompt for approval equally, or be auto-approved if permissions are set.

Error Messages/Logs

Error 1 — get_design_context (Node: 2226:5110, attempt 1)                                                                                     
  The user doesn't want to proceed with this tool use. The tool use was rejected                                                                
  (eg. if it was a file edit, the new_string was NOT written to the file).                                                                      
  STOP what you are doing and wait for the user to tell you how to proceed.                                                                     
                                                                                                                                                
  Error 2 — get_design_context (Node: 2194:7048, attempt 1)                                                                                     
  The user doesn't want to proceed with this tool use. The tool use was rejected                                                                
  (eg. if it was a file edit, the new_string was NOT written to the file).                                                                      
  STOP what you are doing and wait for the user to tell you how to proceed.                                                                     
                                                                           
  Error 3 — get_design_context (Node: 2226:5110, attempt 2 — after re-sharing URL)                                                              
  The user doesn't want to proceed with this tool use. The tool use was rejected                                                                
  (eg. if it was a file edit, the new_string was NOT written to the file).      
  STOP what you are doing and wait for the user to tell you how to proceed.                                                                     
                                                                           
  ---                                                                                                                                           
  Key observation to include in report:                                                                                                         
                                       
  ▎ The error message says "the user doesn't want to proceed" — but the user never saw a prompt to approve or deny. The rejection happened      
  automatically/silently. get_screenshot (called in the same session, same MCP server) was never rejected and worked every time. On the 4th     
  attempt (after user typed "claude resume"), get_design_context succeeded without any change in permissions — confirming it's an 
  intermittent/inconsistent permission prompt issue, not a tool or auth failure.

Steps to Reproduce

Steps to Reproduce:

  • Open Claude Code CLI
  • Connect Figma MCP server (verify it works — get_screenshot should succeed)
  • Paste any valid Figma URL in the chat
  • Claude calls get_screenshot and get_design_context in parallel
  • get_screenshot succeeds immediately
  • get_design_context is silently rejected — no prompt shown to user
  • Retry the same request
  • get_design_context is rejected again with the same error
  • Ask Claude to explicitly retry (e.g. say "resume" or "try again")
  • get_design_context now succeeds — nothing was changed between attempts
  • Same pattern observed with Jira MCP tools in a separate session

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.81

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Cursor

Additional Information

Additional Notes:

  • This is not an authentication or connectivity issue — the tools succeed on retry
  • This is not user error — no prompt was shown to deny
  • Both Figma and Jira MCP servers are affected, suggesting this is a Claude Code permission prompt bug, not a server-specific issue
  • get_screenshot from the same Figma MCP server was never affected, only get_design_context

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗