Skip to main content

I’ve had a very confusing week trying to connect components with my team. I’ve been connecting React components, another engineer has been connecting Compose components. I was getting accurate results from the MCP, the other engineer was always only getting HTML/CSS. When I tried a component he connected, I was getting correct Compose code returned. Everyone was confused. Until today…

 

We realized that I was using an older version of the MCP and `get_code` tool, whereas he was using a newer version and `get_design_context` tool. I just connected to the remote MCP which no longer has `get_code` and only has `get_design_context`, and now I’m getting the same results.

 

We’re wondering if there is a bug in `get_design_context`? Can we get the same functionality as the old `get_code`?

 

Thanks!!!

Hi ​@Adam_Butterfield,

 

Thanks for flagging this!

 

We recently renamed our get_code tool to get_design_context.

It’s possible you’re seeing errors if your MCP client hasn’t refreshed its tools list recently.

Could you please try reconnecting to the server to see if that resolves the issue? If the issue persists, please let us know. I’ll pass this along to our team for further investigation.

Here’s the related documentation for reference: get_design_context

 

Thanks,

Thanks! I think restarting Figma/reconnecting to the local MCP fixed it!
 

I’m still having an issue with the remote MCP though. I only started using it today so not sure if it was ever working correctly. But it seems I can never get the Compose code returned...

Oh! Another thing that might have fixed it too:

Initially I connected components through the UI with a connected GitHub repo. Then we realized we need to provide the detailed prop mapping to get better code generation. The component that was giving me problems just now still had the old connection made through the UI, and it seemed to be using that connection no matter what framework/language was provided (`get_code_connect_map` tool was returning "version": "component_browser" for that node). 

I removed the old connection, unpublished and then republished, and after that it was working.

I battled with this get_design_context failing all day yesterday. After regenerating personal access tokens, disabling Figma integrations in Claude Code, VS Code, and reenabling, none of which had any impact, the steps that resolved this for me:

  1. confirmed in this forum post that `get_code` is deprecated (expected to find documentation eg here)
  2. disabled local MCP server in all files in my Figma Desktop
  3. quit and restarted Figma Desktop
  4. re-enabled MCP server in Figma Desktop

and now my coding agents can successfully `get_design_context`

 

Terms & ConditionsCookie settingsAccessibility statement