Skip to main content
Evan Slawski
Evan Slawski
New Member
Oct 27, 2026 4:38 PM UTC
Solved

Remote MCP omits Code Connect snippets for library instances in consumer files

 

Summary

The remote Figma MCP server's get_design_context returns no code connect snippets (ie. <CodeConnectSnippet\>) for an instance of a published library component when the instance sits in a different file from the library. It returns the usual React + tailwind generated code instead. For the same node, the Figma desktop MCP server's get_design_context returns the correct snippet(s). The remote server's get_code_connect_map also resolves the mapping correctly. Only the remote server's get_design_context drops it.

 

Steps to reproduce

1. In library file A, publish a component set with a Code Connect mapping.
2. In consumer file B, add library A and place one instance of that component, with no overrides.
3. Call get_design_context on the instance through the remote MCP server. Observe code connect snippets are NOT included 👎.
4. Call get_design_context on the same instance through the desktop MCP server. Observe code connect snippets are included 👍.

 

Expected

Step 3 should return code connect snippets (ie. relevant components wrapped in <CodeConnectSnippet\>).

 

Actual

- Instance in consumer file B:
  - ❌ Remote get_design_context: React + Tailwind, no snippet
  - ✅ Desktop get_design_context: correct snippet
  - ✅ Remote get_code_connect_map**: mapping returned
- Instance in library file A:
  - ✅ Remote get_design_context: correct snippet
  - ✅ Remote get_code_connect_map: mapping returned
- Main component in library file A
  - ✅ Remote get_design_context: correct snippet

 

Environment

- Plan: Enterprise, Full seat, Dev Mode
- Remote MCP server: https://mcp.figma.com/mcp
- Desktop MCP server: http://127.0.0.1:3845/mcp, Figma desktop 126.10.13
- MCP client: Claude Code, and Cursor
- Code Connect CLI: 2.0.2

 

Workarounds

- Use the desktop MCP. Not ideal since nearly all onboarding instructions point using the remote MCP.
- AGENTS.md instruction to ensure get_code_connect_map is called on the same node next to get_design_context and substitute its snippets by node ID
 

    adamsmasher
    adamsmasherSolution
    Figmate
    Oct 28, 2026 9:40 PM UTC

    Hi again ​@Evan Slawski - thanks for the detailed report and for documenting a temporary solution.

     

    Our team identified an issue that caused the remote server’s get_design_context to omit Code Connect snippets for components from another library file. Fortunately, a fix was deployed today!

     

    Could you try the same instance in your consumer file again through the remote server? It should now include the Code Connect snippet. If it’s still missing, let me know and we can investigate further.

    View in thread

    1 reply

    adamsmasher
    Figmate
    adamsmasherSolution
    Figmate
    Oct 28, 2026 9:40 PM UTC

    Hi again ​@Evan Slawski - thanks for the detailed report and for documenting a temporary solution.

     

    Our team identified an issue that caused the remote server’s get_design_context to omit Code Connect snippets for components from another library file. Fortunately, a fix was deployed today!

     

    Could you try the same instance in your consumer file again through the remote server? It should now include the Code Connect snippet. If it’s still missing, let me know and we can investigate further.

    Terms & ConditionsAccessibility statement