Head to head · Design components · October 2026 research run

Astryx vs Framelink MCP for Figma

Astryx scores 71.7 (BB) on agent readiness against Framelink MCP for Figma's 69.8 (B), and leads in 4 of 7 scored categories. Framelink MCP for Figma leads on reliability and agent ergonomics. Both do design components.

Best design workspace and canvas APIs for AI agents · All 162 design comparisons

Which one, for what

Astryx BB

Best for Coding agents building React 19 interfaces that want a component library they can query for props, templates and themes.

Ahead on

  • Security & auth, 61 against 55
  • Maintenance & community, 75 against 41
  • Transparency & trust, 64 against 47

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it
  • A hosted endpoint, with nothing to install

Watch for

Version 0.7.x and called a beta in the README and on the home page. Charts are published only under the canary tag

Framelink MCP for Figma B

Best for Reading a Figma frame into a coding agent to build matching UI.

Ahead on

  • Reliability, 68 against 62
  • Agent ergonomics, 83 against 65

Watch for

Last release 0.13.2 on 18 June 2026, and still below 1.0

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Astryx +34

Astryx 75

v0.7.16 tagged on 13 November 2026, five days before this check, with commits on main on 18 November (30). Five or more releases in the last 90 days, including v0.7.10 on 6 November and v0.7.13 to v0.7.16 from 10 to 13 November (20). 348 open issues and 704 open pull requests on 18 November. Of the 25 newest issues, opened 16 to 18 November, 14 had a reply and many carried a lane label (15 of 25). No Astryx entry in the official MCP registry, searched for astryx and astryxdesign on 18 November (0 of 15). Dependabot, a pinned pnpm lockfile and CI workflows (10). Total 75.

Framelink MCP for Figma 41

Last release 0.13.2 on 18 June 2026, 141 days before this check (10). No release in the 90 days since 8 August (0). The maintainer merged his own pull requests through June and closed four outside pull requests between July and September, but the three open issues filed since May have no reply and seven outside pull requests from July to October are open without one (8 of 25). In the official MCP registry under the GitHub-verified namespace io.github.GLips, with 0.13.2 as the latest entry (15). CI and tests exist, and the MCP SDK is pinned at 1.29.0 with current dependencies (8 of 10). 10 + 0 + 8 + 15 + 8 = 41.

Agent ergonomics Framelink MCP for Figma +18

Astryx 65

Read from source, not from a run. The local server lists 31 tools (5), with 10 back for --docs-only, a nine-tool read-only subset (15 of 25). --limit on search, build and discover, a domain filter on search, and --detail and --dense to size answers, but no paging (16 of 20). A failing command returns its JSON error with isError, and errors carry codes and suggested fixes (18 of 20). No readOnlyHint or destructiveHint annotations. Template, swizzle and theme writes refuse to overwrite without --overwrite, and integration add has --dry-run (8 of 20). Few required inputs, but JavaScript only (8 of 15). Total 65.

Framelink MCP for Figma 83

Two compact tools (25). Output is sized by nodeId and depth, and the default tree format drops default values and auto-generated layer names and deduplicates repeated styles and subtrees. No pagination, which a single-file read rarely needs (16 of 20). Errors are written for a model to recover from, with Figma's 403 body surfaced and guidance for wrong node IDs from prototype, branch and FigJam links, per the 0.12.0 changelog (16 of 20). get_figma_data carries readOnlyHint and download_figma_images openWorldHint, with no destructiveHint on the tool that writes files and no note on overwriting (14 of 20). Only fileKey is required and one npx line starts it, but there is no SDK, which a two-tool local server doesn't need (12 of 15). 25 + 16 + 16 + 14 + 12 = 83.

Transparency & trust Astryx +17

Astryx 64

MIT (30). The docs site links Meta Open Source's privacy policy (effective 25 April 2023), which covers the site and its services, names Google Analytics cookies and keeps data until it's no longer needed, with no periods. It excludes the open-source code and doesn't mention the hosted MCP server (12 of 30). Deprecations are dated in the changelog with a named replacement and a removal release, breaking changes come with codemods, and SECURITY.md says only the latest release gets fixes. The Component Lifecycle wiki page wasn't read (14 of 20). No telemetry code was found in the CLI source, and network calls happen only on commands that fetch (theme add, blog), but no statement says so (14 of 20). Total 70.

Framelink MCP for Figma 47

MIT licence in the repository and on npm (30). No privacy policy or terms on framelink.ai or the docs. Design data goes from Figma to the local model client, and the docs describe what telemetry sends, but there is no data statement to agree with (8 of 30). No deprecation policy. Breaking defaults are called out in the changelog (5 of 20). Telemetry to PostHog (us.i.posthog.com) has been on by default since 0.10.0 on 10 April 2026. The configuration page discloses it with three ways to opt out, while the README doesn't mention it, and an open issue of 16 April 2026 reports that error_message can include file keys and node IDs, which the source's redaction (credentials only) doesn't cover (14 of 20). 30 + 8 + 5 + 14 = 57.

Reliability Framelink MCP for Figma +6

Astryx 62

Scored as a local package, since the owner runs it. Official npm packages with Node 22.13 or later and React 19 or later stated (20). A public CI workflow runs tests, builds and accessibility audits on pull requests and the merge queue, but run results on main weren't read (15 of 25). The repository had 348 open issues on 18 November 2026. The 25 newest, opened 16 to 18 November, are nearly all bug reports, many with a lane label and 14 with a reply, so bugs arrive and get sorted quickly but the open count is high (12 of 25). Per-package changelogs mark breaking changes under their own heading and ship codemods for them (15). Version 0.7.x, called a beta in the README and on the home page (0). Total 62.

Framelink MCP for Figma 68

Read with the local-software lines, because the server runs on the user's machine and calls the Figma REST API. Installs from the official npm package figma-developer-mcp, with Node 20.20 or later stated in package.json (20). A CI workflow runs prettier, eslint, a type check and the vitest suite, but only on pull requests, and the five newest runs (outside pull requests from 22 August to 2 October) all failed, so passing on the default branch couldn't be confirmed (15). Eight open issues, the oldest open one a 429 rate-limit thread from November 2025 with 30 comments, and nothing open that reports a crash in the current release (18). Release-please changelog with semver tags and breaking defaults called out, such as the switch to tree output in 0.13.0 (15). Version 0.13.2, below 1.0 and not declared stable (0). 20 + 15 + 18 + 15 + 0 = 68.

Security & auth Astryx +6

Astryx 61

Local software with no credentials, so the middle band, as for other keyless local tools (20). --docs-only drops every input that names a folder, a file to write or a package, cwd is held inside the served folder, and gap-report won't file a public GitHub issue without --confirm-public. Other writes have no approval step (14 of 20). Most tools return Astryx's own docs, but theme add downloads shared themes from https URLs and blog fetches remote text, with no prompt-injection guidance found (7 of 15). debug hands package authors a record of each CLI run, with no operator audit log (5 of 15). SECURITY.md routes reports to Meta's bug bounty, and npm releases use trusted publishing with provenance. astryx.atmeta.com serves no security.txt (15 of 20). Total 61.

Framelink MCP for Figma 55

The credential is the user's own Figma token. Figma personal access tokens are scoped and revocable, and the docs say file_content:read is the one scope the server needs. OAuth tokens are accepted but not refreshed, and the token is passed in the client config's args or env, not a URL (25 of 30). The server only reads Figma. Its one write is image files, confined to --image-dir, and --skip-image-downloads removes that tool; the local HTTP mode has no authentication of its own and binds 127.0.0.1 by default (16 of 20). Layer names and text written by collaborators reach the model as they are, and no prompt-injection guidance was found (3 of 15). Logs go to the local console only, with no per-call audit record (3 of 15). SECURITY.md asks for private reports through GitHub security advisories with a 48-hour acknowledgement. No security.txt, bug bounty or certification (8 of 20). 25 + 16 + 3 + 3 + 8 = 55.

Score by category

CategoryWeightAstryxFramelink MCP for FigmaEdge
Reliability16%6268Framelink MCP for Figma +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9087Astryx +3
Agent ergonomics13%6583Framelink MCP for Figma +18
Security & auth14%6155Astryx +6
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7541Astryx +34
Transparency & trust7%6447Astryx +17
Negative events≤1500
TotalBB 71.7/100B 69.8/100

Facts side by side

FactAstryxFramelink MCP for Figma
KindSDK + MCPMCP server
VendorMetaFramelink (Graham Lipsman)
Hosted endpointhttps://astryx.atmeta.com/mcpno (local only)
Transportsstdio, Streamable HTTPstdio, Streamable HTTP
AuthNoneToken
PricingFreeFree
x402nono
LicenceMITMIT
Tools exposed312
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedio.github.GLips/Figma-Context-MCP
Last release2026-11-132026-06-18
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Popularity31k stars16k stars, 162k npm/wk

How the scores have moved

Verdicts

Astryx

Astryx gives a coding agent typed MCP tools to search components, read docs and build themes, with no account and an MIT licence, and Meta tagged four releases from 10 to 13 November 2026. It is a 0.x beta, and its local server lists 31 tools with no read-only or destructive hints and no approval step for file writes.

Framelink MCP for Figma

Two compact, typed tools return Figma layout and styles in a token-saving tree format and save image assets, with a read-only hint and a flag that removes the writing tool. There has been no release since 18 June 2026, issues and outside pull requests since July have gone unanswered, and telemetry is on by default.

Before you call either

Astryx

  1. Run astryx directly when you can run commands. Use astryx mcp only from a client that reaches tools through MCP
  2. Use astryx mcp --docs-only or https://astryx.atmeta.com/mcp when you only need to look things up, since those tools can't write files
  3. Pass --limit to search, build and discover, and --detail or --dense, to keep answers small
  4. Before theme add from a URL, check the source, because a shared theme is downloaded and installed into the project
  5. Read the code in a failed tool's JSON error and follow its suggested fix before retrying

Framelink MCP for Figma

  1. Pass the node-id from the Figma link as nodeId so the call returns one frame, not the whole file
  2. Leave depth unset unless the user asks, as the tool description says
  3. Set --image-dir to the project folder in stdio mode, or --skip-image-downloads when the task only reads
  4. Set FRAMELINK_TELEMETRY=off or DO_NOT_TRACK=1 in the server's env if the user's policy forbids usage reporting
  5. On a 429 from Figma, wait and retry later; the limit is the user's Figma plan, not the server's

Questions

Which is better for AI agents, Astryx or Framelink MCP for Figma?

Astryx scores 71.7 (BB) on agent readiness against Framelink MCP for Figma's 69.8 (B), and leads in 4 of 7 scored categories. Framelink MCP for Figma leads on reliability and agent ergonomics.

Can an agent call Astryx and Framelink MCP for Figma without installing anything?

Astryx has a hosted endpoint at https://astryx.atmeta.com/mcp. Framelink MCP for Figma runs on your own machine, with no hosted endpoint listed.

Are Astryx and Framelink MCP for Figma open source?

Yes. Astryx is open source (MIT). Framelink MCP for Figma is open source (MIT).

Other comparisons with Astryx or Framelink MCP for Figma

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.