Code Connect mappings are not recognized by Figma MCP

Hey ​@Jan Trpkoš, thanks for reaching out!

A couple of things worth ruling out first:

1. Confirm the library is published. If Code Connect is mapped via the CLI but the library containing this component hasn't been published, MCP tools won't be able to see those mappings yet. Even though they show up correctly in the web app.
2. Check whether the nested components have their own mappings. If a component (like an icon) is nested inside this one, it needs its own separate Code Connect mapping to show as connected. get_code_connect_suggestions flagging it otherwise may be accurate rather than a bug, if that inner piece was never mapped on its own.

Have you tried calling these tools against an instance of the component (one placed in a file that consumes the library), rather than the component itself? Selection type has affected Code Connect visibility in MCP before, so it's worth testing both if you haven't already.

For more on how Code Connect and the Figma MCP server work together, take a look at our Guide to the Figma MCP server.

I checked all three things:

All nested components are also mapped with Code Connect.
The library is published.
I tried both the original component and an instance of it.

Unfortunately, I’m still seeing the same behavior: get_code_connect_map returns {}, and get_design_context returns generated/raw layout code instead of the connected component.

Hi ​@Jan Trpkoš, thanks for checking so quickly! 

I’m Denise from the Community team, and I work with ​@Gayani_S. This rules out a few things, so I'd like to check the following next:

1. The label needs to be an exact match. On the remote server, codeConnectLabel has to match the label string in the Code Connect UI character-for-character. It's the second field when you view the mapping in Dev Mode, not the framework name. If your team's label is something like React Web or DS React, passing "React" won't match and you'll get {} back. Worth grabbing the exact string and trying that. (Also note clientFrameworks and clientLanguages don't filter this particular tool, in case those were in the mix.)

2. Which server and client are you on? Remote MCP or the desktop server, and which IDE/agent? If it's the desktop server, could you also confirm your Figma desktop app version is current? Behavior has differed between clients before, so this narrows things down fast.

3. Any chance there's a proxy or firewall in play? We've seen setups where every other MCP call works fine but Code Connect specifically comes back empty because the request is being filtered. A good tell: does npx figma connect publish --verbose run cleanly on the same machine and network?

4. Is the MCP session authenticated as the same account that can see the library? If the token is scoped to a different org or team than the one hosting the library, the mappings won't be visible to the tool even though they're fine in the web app.

If you can share a node-specific URL (the one with node-id= in it) for a component you'd expect to come back mapped, plus the exact label string, We’d happy to take a closer look and escalate with those details to our Technical Quality team. 

Hi
Here are the requested details:

• Node URL: node-specific URL
• Exact label:  React 

Also.

1. The CLI configuration uses  label: React and  codeConnectLabel: React
2. The remote MCP server at  https://mcp.figma.com/mcp  is used through GitHub Copilot CLI. The Figma Desktop MCP server is not used.
3. No proxy is configured through environment variables or WinHTTP. A targeted  npx figma connect publish --verbose  for this exact component completed validation and upload successfully on the same machine and network.
4. The MCP session is authenticated as jantr@axis.com , with a Full seat in 2N TELEKOMUNIKACE a.s.  The same account has access to the library in the Figma web app.

Hi, ​@Jan Trpkoš 👋 Picking this up for my teammates. Thanks for the follow ups to ​@djv’s questions. Very helpful. I took this to our team for guidance. We’ll follow up here as soon as there is an update. — Jaycee