Skip to main content
Question

Local MCP sometimes has a timeout. How to debug?

  • October 29, 2025
  • 1 reply
  • 44 views
Brad Momberger

I’ve been working with the Figma app’s MCP Service in Copilot Agent mode, but I have the occasional timeout after 30+ seconds even though it doesn’t seem like Figma should be blocked by anything.  Has anyone seen the same and figured out what’s causing it? Alternately, is it possible to see logging from the MCP server process?

 

Thanks.

Mike Dane

1 reply

J
Figmate
  • Junko3
  • Figmate
  • October 30, 2025

Hi ​@Brad Momberger,
 

I understand you’re running into timeout issues. Just to confirm, your setup is using the Figma desktop MCP server with VS Code and Copilot, is that right?

If so, this might help — here’s how you can save debug logs in VS Code:

  • After reproducing the issue in VS Code, open the Command Palette using Cmd + Shift + P (Mac) or Ctrl + Shift + P (Windows) and search for “Figma: Save Debug Information.”
  • Click “Continue” in the pop-up to select a location on your computer to save the logs.

Here are also a few basic troubleshooting steps you can try:

  • Check if there are any updates available
  • Try logging out of your Figma account in VS Code and then logging back in
  • If you’re using a VPN or proxy, make sure figma.com is added to your safe list

In the meantime, if the issue continues and you’re open to it, you can contact our Support team directly via this secure form: Submit a request, so they can investigate further.

When submitting the form, please include:

  • A screen recording showing this behavior, with the entire window in frame

Our team uses these recordings to try reproducing the issue in our own environment, so showing all steps and windows will be extremely helpful.

 

Thanks,

Terms & ConditionsCookie settingsAccessibility statement