Feature request
get_code_connect_map (Figma MCP) currently returns an empty map {} with success semantics in at least three distinct situations:
- The queried fileKey has no published Code Connect — typically because the caller passed the fileKey of a design file that instantiates the components, rather than the library file the mappings were published against. Response: bare
{}.
- The node genuinely has no mappings. Response: bare
{}.
- The backend lookup timed out — e.g. when the queried node is too broad (page/document root on a large file). Response:
{} plus only a prose note appended to the result: "Note: the Code Connect lookup timed out, so this response may be missing Code Connect data." (reproduced 2/2).
For MCP clients — especially agents — 1 and 3 are indistinguishable from 2. The practical failure mode is an agent confidently concluding "this component has no Code Connect mapping" and writing that into downstream code or docs, when the mappings exist and the call was merely mis-scoped or timed out. Since passing a design-file key is the natural first attempt (it's the fileKey the caller is holding), case 1 is the default path for anyone who doesn't already know the library fileKey.
Request: make the outcomes distinguishable. Any of these would work for MCP clients:
- an error (or MCP tool error result) for "this file has no Code Connect published" and for "lookup timed out", or
- a machine-readable
status field alongside the map (ok / no_code_connect_for_file / timeout_partial), keeping {} only for a genuine empty result.
Scope note: I'm aware #284 was routed away as an MCP-server issue, but #373 (MCP response shape) was fixed via this repo, so filing here for the paper trail — happy to move this to the right channel if there is one.
Related, not duplicates: #340 (MCP silently ignores Angular mappings), #292 (placeholder snippets), forum threads 42405 and 56495 (empty/partial maps with different root causes — those are about missing entries, this one is about failure modes being unsignaled).
Feature request
get_code_connect_map(Figma MCP) currently returns an empty map{}with success semantics in at least three distinct situations:{}.{}.{}plus only a prose note appended to the result: "Note: the Code Connect lookup timed out, so this response may be missing Code Connect data." (reproduced 2/2).For MCP clients — especially agents — 1 and 3 are indistinguishable from 2. The practical failure mode is an agent confidently concluding "this component has no Code Connect mapping" and writing that into downstream code or docs, when the mappings exist and the call was merely mis-scoped or timed out. Since passing a design-file key is the natural first attempt (it's the fileKey the caller is holding), case 1 is the default path for anyone who doesn't already know the library fileKey.
Request: make the outcomes distinguishable. Any of these would work for MCP clients:
statusfield alongside the map (ok/no_code_connect_for_file/timeout_partial), keeping{}only for a genuine empty result.Scope note: I'm aware #284 was routed away as an MCP-server issue, but #373 (MCP response shape) was fixed via this repo, so filing here for the paper trail — happy to move this to the right channel if there is one.
Related, not duplicates: #340 (MCP silently ignores Angular mappings), #292 (placeholder snippets), forum threads 42405 and 56495 (empty/partial maps with different root causes — those are about missing entries, this one is about failure modes being unsignaled).