I’m seeing a mismatch between SVGs returned through Figma MCP and SVGs exported directly from the Figma UI.
What I expected
When I request a vector/component asset through MCP, I expected the SVG export to preserve the same export box/canvas as the original Figma component/frame export.
What happens instead
The SVG asset returned through MCP appears to be tightly cropped to the inner vector path bounds, while the direct SVG export from Figma keeps the full component canvas.
Concrete example
I have an alphabet component where each letter is designed inside a 42x42 frame/component.
- the MCP asset is cropped to the actual stroke bounds
- the direct Figma export preserves the full 42x42 canvas and empty space/padding
Why this matters
This breaks 1:1 implementation workflows when layout depends on the original component export box. In my case, letters are placed inside fixed-size crossword cells, and the MCP-exported SVGs no longer align visually the same way as the Figma design.
Question
Is this expected MCP behavior, or is this a bug?
If expected:
- is there any MCP option to export the full component/frame bounds instead of tight vector bounds?
- is there a recommended MCP workflow to get the same SVG output as “Export as SVG” in the Figma UI?
If unintended:
- it would be helpful for MCP asset export to support preserving the original node/component export frame.
Environment
- Using Figma MCP via get_design_context
- Comparing returned asset URLs vs direct SVG export from the Figma editor UI