Agent does not invoke Figma MCP tools (get_screenshot, get_design_context) despite server connected and tools loaded

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor IDE — Chat / Agent (with Figma MCP integration enabled)

Describe the Bug

When the user asks the agent to call Figma MCP tools (e.g. get_screenshot or get_design_context) with a valid Figma file key and node ID, the agent responds that it does not have access to these tools or cannot invoke them. Meanwhile:

  • Figma MCP integration is enabled in Cursor (green status).
  • MCP logs show the Figma server connects successfully and 12 tools are listed every time (listOfferings: Found 12 tools).
  • No “Tool not found” or connection errors appear in the MCP output.

So the tools are available to Cursor, but the agent does not receive or does not use them when the user explicitly requests e.g. “Call get_screenshot for file c0HCGiN4rQGOe4WFwfnMuY, node-id 3:7”.

Steps to Reproduce

  1. Enable Figma MCP in Cursor (Settings / Integrations). Ensure it shows as connected (green indicator).
  2. Open a new chat (or Composer).
  3. Send a message such as:
    “Call get_screenshot for file c0HCGiN4rQGOe4WFwfnMuY, node-id 3:7”
    or:
    “Use the Figma integration: get_screenshot for file c0HCGiN4rQGOe4WFwfnMuY, node 3:7”
  4. Observe the agent’s response.

Expected Behavior

  • The agent should recognize that Figma MCP is enabled and that get_screenshot is available.
  • The agent should invoke get_screenshot with the given fileKey and nodeId and return the screenshot (or an error from the Figma API) in the chat.

Screenshots / Screen Recordings

figma-mcp-log.txt (172 KB)

Operating System

Linux

Version Information

Version: 2.5.17
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.17.0-14-generic

For AI issues: add Request ID with privacy disabled

abd4298c-3bc3-46ca-badf-3349f5c36f9f

Additional Information

No CallTool / tool execution entries for get_screenshot or get_design_context when the user asks for a screenshot.

So: tools are loaded on the Cursor/MCP side, but the agent in the chat session does not get or use them.

Workarounds Tried

  • Opening a new chat and re-asking the same request.
  • Restarting Cursor.
  • Confirming Figma MCP is enabled and shows 12 tools in Output → MCP (user-figma).
  • Explicitly naming the tool and parameters in the prompt.

None of these led to the agent invoking the tool.

Does this stop you from using Cursor

No - Cursor works, but with this issue

figma-mcp-log.txt (172,4 КБ)

4

Hey, thanks for the report. This is a known issue. The MCP server connects and finds tools on the client side, but they don’t make it into the toolset the agent gets on the backend. The team is aware, but there’s no ETA for a fix yet.

A few things to try:

  1. Update Cursor to the latest version. You’re on 2.5.17. It won’t necessarily fix this specific bug, but it might help.

  2. Toggle MCP off and on in Cursor Settings > Tools & MCP. Turn off Figma MCP, wait a couple seconds, then turn it back on. After that, open a new chat. For some users, even toggling any other MCP helps since it forces all servers to reinitialize.

  3. Try a project-level config instead of a global one. Add .cursor/mcp.json at the project root with the same Figma config. For some users, this works more reliably.

  4. Wait a bit after connecting. There can be a delay between the UI showing the server as connected (green) and the agent actually getting access to the tools. Sometimes waiting helps.

I can see you already tried a new chat, a restart, and explicitly listing the tools in the prompt. If toggling and updating still don’t help, let me know.

Related threads:

1 Like
5

Thank you very much, I updated the app to the latest version and rebooted MCP Figma server. After that agent was able to perform a screenshot.

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.