Skip to content

Releases: s9hn/figma-compaction-mcp

v3.0.2

Choose a tag to compare

@s9hn s9hn released this 15 May 01:23

3.0.2

Documentation patch release.

Changed

  • Updated README version references to 3.0.2.

Validation

  • npm test
  • npm run build
  • npm pack --dry-run

v3.0.1

Choose a tag to compare

@s9hn s9hn released this 15 May 00:57

3.0.1

Patch release for compact fidelity on tall Figma screens.

Fixed

  • Supplement metadata-derived text samples across tall screens so lower design cases remain visible after compaction.
  • Add text coverage quality markers and warnings when compact output requires metadata supplementation.
  • Return fallback for metadata-only compact output without usable implementation payload lines.
  • Expand sparse section responses by fetching eligible child design contexts before compaction.

Validation

  • npm test
  • npm run build
  • npm pack --dry-run
  • Live token audit for node 4:4377: 52,788 raw tokens to 3,823 compact tokens, 92.76% reduction, with photo/document/pdf lower cases present.

v3.0.0

Choose a tag to compare

@s9hn s9hn released this 30 Apr 02:28

Breaking Changes

  • Renamed the npm package from figma-to-markdown-mcp to figma-compaction-mcp.
  • Renamed the recommended MCP server id from figma-to-markdown to figma-compaction.
  • Replaced get_figma_as_markdown with get_figma_compact_context as the public MCP entrypoint.
  • Removed the Markdown-oriented public output contract in favor of compact plain-text context only.

Highlights

  • Promoted compact plain-text context to the only public caller-facing contract.
  • Split parsing and compaction into dedicated analyzer and serializer modules for clearer transport boundaries.
  • Reworked README, README.ko, AGENTS, SPEC, tests, and package metadata around the compact-context-first workflow.
  • Added a live compact fidelity audit script and regression coverage for retained text, typography, assets, truncation, and fallback behavior.
  • Expanded CI to run npm test and npm run build on Node 18, 20, and 22, plus npm pack --dry-run on Node 22.

Migration

  1. Install the new package with npm install -g figma-compaction-mcp or switch your MCP client to npx -y figma-compaction-mcp.
  2. Update MCP registrations, prompts, and automation to use figma-compaction and call get_figma_compact_context first.
  3. Update hard-coded repository links to https://github.com/s9hn/figma-compaction-mcp.

Validation

  • Local: npm test, npm run build, npm pack --dry-run
  • GitHub Actions: run 25144187171 succeeded on Node 18, 20, and 22
  • npm: published figma-compaction-mcp@3.0.0 with tag latest

v2.0.0 — Bridge Simplification And Output Budget Update

Choose a tag to compare

@s9hn s9hn released this 27 Apr 01:47

Highlights

  • Removed the legacy raw-JSON MCP tool and narrowed the public interface to the Figma URL bridge workflow.
  • Changed max_output_chars so truncation is opt-in instead of applied by default.
  • Reworked the README around token reduction, architecture, setup, and MCP client registration.
  • Fixed CI to install dependencies before running tests.

Verification

  • npm test
  • npm run build
  • npm pack --dry-run

v1.1.1 — Metadata And Repo Cleanup

Choose a tag to compare

@s9hn s9hn released this 27 Apr 00:54

figma-to-markdown-mcp v1.1.1

Patch release focused on package metadata and repository cleanup after the bridge release.

What changed

  • Restored npm package metadata fields such as repository, homepage, bugs, license, author, and engines
  • Added AGENTS.md so repository guidance ships alongside the bridge-based workflow update
  • Restored a fuller repository .gitignore so local artifacts are filtered more consistently during development and release work
  • Bumped package, runtime, and repository version references to 1.1.1

Notes

This release does not change the bridge runtime behavior introduced in 1.1.0. It aligns npm, GitHub, and repository metadata so the new bridge release line is packaged and documented consistently.

Installation

npm install -g figma-to-markdown-mcp

npm package

Full Changelog

v1.1.0 — Internal Figma MCP Bridge

Choose a tag to compare

@s9hn s9hn released this 27 Apr 00:54

figma-to-markdown-mcp v1.1.0

Minor release introducing an internal Figma MCP bridge for Figma-link workflows.

What changed

  • Added get_figma_as_markdown, a URL-based MCP tool that fetches Figma context internally and returns compacted Markdown instead of raw upstream payloads
  • Added an internal Figma MCP client with Streamable HTTP first and SSE fallback support for local desktop MCP connections
  • Added compaction for upstream get_design_context and get_metadata output before it reaches the calling agent
  • Added bridge fallback handoff output so agents can continue with the standard Figma MCP tools when internal fetch or compaction cannot safely complete
  • Added upstream tool error handling, alternate nodeId retry, and optional metadata handling for more reliable bridge execution
  • Added tests covering compacted success flow and bridge fallback behavior

Notes

This release changes the primary Figma-link workflow. Agents should call get_figma_as_markdown first, consume the compacted Markdown when the bridge succeeds, and only continue with direct Figma MCP tools when the bridge explicitly returns a fallback handoff.

Installation

npm install -g figma-to-markdown-mcp

npm package

Full Changelog

v1.0.2 — npm Metadata Fixes

Choose a tag to compare

@s9hn s9hn released this 24 Apr 02:08

figma-to-markdown-mcp v1.0.2

Patch release focused on npm publish metadata normalization.

What changed

  • Normalized the npm bin entry to src/index.js
  • Normalized repository.url to the canonical git+https form expected by npm
  • Bumped package and runtime version strings to 1.0.2
  • Updated the repository docs for the 1.0.2 release

Notes

This release does not change the get_design_context_compact tool behavior. It removes the npm publish-time package warnings seen in 1.0.1 and keeps GitHub, npm, and runtime version metadata aligned.

Installation

npx figma-to-markdown-mcp

npm package

Full Changelog

v1.0.1 — Metadata Alignment

Choose a tag to compare

@s9hn s9hn released this 24 Apr 01:56

figma-to-markdown-mcp v1.0.1

Patch release focused on version metadata alignment across the repository, runtime, and published release surfaces.

What changed

  • Bumped package and runtime version strings to 1.0.1
  • Updated the README version reference to 1.0.1
  • Added the 1.0.1 changelog entry for repository release tracking
  • Created the matching GitHub release entry for the v1.0.1 tag

Notes

This release does not change the get_design_context_compact tool behavior. It aligns npm metadata, runtime-reported version strings, repository docs, and GitHub release metadata so the published version is reported consistently everywhere.

Installation

npx figma-to-markdown-mcp

npm package

Full Changelog

v1.0.0 — Initial Release

Choose a tag to compare

@s9hn s9hn released this 24 Apr 00:23

figma-to-markdown-mcp v1.0.0

Initial public release.

What it does

A compact markdown layer in front of Figma MCP for AI implementation workflows.

Accepts a Figma node URL, calls Figma Desktop MCP get_design_context internally, and returns compact markdown — stripping out raw React/Tailwind passthrough that inflates token cost without adding implementation value.

~45% token reduction on typical design context payloads (sample: 1,053 → 582 tokens).

Added

  • get_design_context_compact tool
  • Automatic compaction of raw React/Tailwind passthrough
  • Layout, text, typography, asset, and implementation note extraction
  • ## QA Flags section surfaced when compaction confidence is low
  • Raw fallback returned when compaction fails
  • include_stats parameter for token size reporting
  • Support for both Content-Length and JSON-line MCP transport framing
  • Branch URL support for Figma branch links
  • Node.js 18+ compatibility

Installation

npx figma-to-markdown-mcp

npm package