Can't get code connect map info from Figma Remote MCP server

I've made some progress on this issue. After publishing my component library as a published library in Figma, the get_code_connect_map tool now works correctly on the remote MCP server and returns the expected mapping data.

  However, I'm still encountering an issue with get_design_context - it does not include any Code Connect information in its response, even though get_code_connect_map successfully retrieves the mappings for the same node.

  To summarize:
  - get_code_connect_map → ✅ Works correctly after using published library
  - get_design_context → ❌ Still returns no Code Connect information

  Is this expected behavior? I assumed that get_design_context would also leverage the Code Connect mappings to provide component information in its response. Could someone clarify whether Code Connect data should be included in get_design_context output, or if these two tools serve different purposes?

  Any guidance would be appreciated. Thanks!

Hi ​@cordTan, thanks for reaching out and apologies for the delayed reply! 

We were experiencing a service disruption with get_design_context right around the time you posted this topic. Have you refreshed your tabs recently? And are you still experiencing the same issue since? 

Please let us know if you are, and we can flag this over to the MCP team to investigate further. 

Hi,

I have the same issue:

 - get_code_connect_map → ✅ Works correctly after using published library
  - get_design_context → ❌ Still returns no Code Connect information

But with the local MCP that is running on the desktop app. Do you know if it’s because the Desktop is not updated yet or is there an other issue ?

Thanks !

Hi ​@Bruce Pauker, thanks for flagging this! 

We did have another service disruption yesterday, but we have since pushed a fix. When was the last time you refreshed your tabs to ensure you’re using the latest version of the app? 

If it’s still not working after a refresh, we’ll better understand if the issue is still lingering. 

Hi ​@djv ,

I just did the refresh and is still not working. I checked that I have the last version of the app and it is the case.

Thanks !

Thanks for confirming, ​@Bruce Pauker! 

When did this issue begin occurring for you? Has this ever worked for you successfully in the past? Have you tried reconnecting to the server to see if that helps at all?

With a few more details, I can pass this onto our MCP team to investigate further.