JSON format structure changed - missing style elements and different DOM structure compared to previous versions？

[iwhalefed007]

Hi there! I've noticed a significant change in the JSON output format from the Figma MCP service over the past few days？

The JSON structure returned by the service has changed dramatically compared to what I was getting about a week ago. The new format is missing many important elements and has a completely different DOM structure.
What changed:
Before (1 week ago): JSON had nodes structure with complete document objects, detailed style properties, absoluteBoundingBox, constraints, effects, interactions, overrides, etc.
Now (recent): JSON uses mainNode structure, missing most detailed properties, only contains basic visual and layout information
Example comparison:

Old format (complete):

{
  "nodes": {
    "2025:16728": {
      "document": {
        "id": "2025:16728",
        "name": "login",
        "type": "FRAME",
        "absoluteBoundingBox": { "x": -1442.0, "y": 17071.0, "width": 375.0, "height": 88.0 },
        "constraints": { "vertical": "TOP", "horizontal": "LEFT" },
        "effects": [...],
        "style": {
          "fontFamily": "SF Pro Text",
          "fontWeight": 700,
          "fontSize": 16.0
        }
      }
    }
  }
}

New format (simplified):

{
  "mainNode": {
    "id": "2025:16728",
    "name": "login",
    "type": "FRAME",
    "dimensions": { "width": 375, "height": 812" }
  }
}

Impact:
This change makes it much harder to implement detailed design-to-code workflows, as we're missing crucial styling and positioning information that was previously available.
Questions:
Is this an intentional change in the API?
Are there different API endpoints or parameters to get the full detailed data?
Is this related to recent Figma API changes?
Can we get the complete data structure back?
Environment:
Service: Figma MCP
Timeframe: Issue appeared in the last 2 days
Previous working version: About 1 week ago
Expected behavior:
Return to the previous detailed JSON format with complete style information, constraints, and DOM structure.

Thanks for looking into this!

[GLips]

Uhh, are you sure you're using the Framelink Figma MCP? Can you share your MCP config details?

[aviral-whalar]

@GLips

Yes, he is 100% using Framelink MCP. Framelink was a gift to our workflow at my current workplace. However since a few weeks ago it's become totally unusable since the JSON returned is totally devoid of details like the token names. We are using style-dictionary such that the tokens we see in figma are directly used in tailwind code like bg-action-primary-background-color-default from the figma token action-primary-background-color-default

Given that the JSON returned no longer has token info, this has become impossible and we have had to switch to manual development.

In our team we couldn't figure out if it's due to updating versions on Figma side and them becoming hostile to other MCPs, or was it just Framelink being buggy.

The Figma-to-code AI workflow we have is not supported by official Figma MCP either, the previous Framelink JSON was perfect.

[aviral-whalar]

For further context, I have already tried everything that the MCP allows like asking for more depth etc, but in the end all I get is

{
  "mainNode": {
    "id": "2025:16728",
    "name": "login",
    "type": "FRAME",
    "dimensions": { "width": 375, "height": 812" }
  }
}

the forbidden JSON that makes life miserable haha

[GLips]

Well shoot. I'm glad Framelink was working so well for you, but this is a bummer for sure. It also makes no sense to me. That structure shouldn't be possible in Framelink. If Figma updated their API the Framelink MCP would just straight up break—we do a full translation from their format into our own. No changes on their end would pass through to the JSON.

Can you get the configuration details your teammate is using? They'll look something like this:

{
  "mcpServers": {
    "Framelink Figma MCP": {
      "command": "npx",
      "args": [
        "-y",
        "figma-developer-mcp",
        "--figma-api-key=YOUR-KEY",
        "--stdio"
      ]
    }
  }
}

[iwhalefed007]

@GLips my MCP config details

{
  "mcpServers": { 
  "Framelink Figma MCP": {
      "command": "npx",
      "args": [
        "-y",
        "figma-developer-mcp",
        "--figma-api-key=figd_s-xxxxx",
        "--stdio"
      ]
    }
  }
}