0.13.1 → 0.13.2
patch release, 18 June 2026No tool definition changed.
MCP servers / figma-developer-mcp
figma-developer-mcp
1 of its last 5 updates changed what the agent reads: 0 tool descriptions rewritten, up to 0.13.2.
npm package · npm page · recorded on 24 October 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. Method and limits.
Release by release
0.13.0 → 0.13.1
patch release, 18 June 2026No tool definition changed.
0.12.0 → 0.13.0
minor release, 18 June 2026No tool definition changed.
0.11.0 → 0.12.0
minor release, 27 May 2026download_figma_images: input schema changed
0.10.1 → 0.11.0
minor release, 20 April 2026No tool definition changed.
Releases tried: 0.10.1 (2026-04-10); 0.11.0 (2026-04-20); 0.12.0 (2026-05-27); 0.13.0 (2026-06-18); 0.13.1 (2026-06-18); 0.13.2 (2026-06-18).
Tools in 0.13.2
The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition.
| Tool | Description | Pin |
|---|---|---|
| get_figma_data | Get comprehensive Figma file data including layout, content, visuals, and component information | fc22456bc32b |
| download_figma_images | Download SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/runner/work/verfy/verfy | 3ed2e56e0809 |
Lock these tools
Pin what figma-developer-mcp serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.
$ pip install verfy
$ verfy lock check --update # shows each tool, then writes verfy.lock
$ git add verfy.lock# .github/workflows/verfy.yml, after actions/checkout
- uses: anvarbekovjavohir277-dot/verfy-action@v1Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.