Head to head · Design files · October 2026 research run

Framelink MCP for Figma vs Magic Patterns

Framelink MCP for Figma scores 66.1 (B) on agent readiness against Magic Patterns's 63.4 (B), and leads in 3 of 7 scored categories. Magic Patterns leads on reliability, maintenance & community and transparency & trust. Both do design files.

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

Which one, for what

Framelink MCP for Figma B

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

Ahead on

  • Agent ergonomics, 83 against 67
  • Payments & pricing, 60 against 23

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

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

Magic Patterns B

Best for Generating and iterating on coded React prototypes from a coding agent, and pulling a design into a codebase.

Ahead on

  • Reliability, 75 against 68
  • Maintenance & community, 70 against 41
  • Transparency & trust, 60 against 47

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

MCP and API-key access need a paid seat, Starter at $20 a month

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.

Payments & pricing Framelink MCP for Figma +37

Framelink MCP for Figma 60

By the self-hosted rule. A free MIT package with nothing to buy (20 + 20 + 20), and no payment protocol (0). Figma API use falls under the user's own Figma plan. 60.

Magic Patterns 23

No x402, MPP or L402. A 402 means out of credits, with no payment requirements (0). Seat prices are public and the on-demand rate is $0.02 a credit, but a generation's credit cost isn't known before it runs (typical 70 per generation per the docs), so between plan-only and per-unit (15 of 20). The MCP overview and the plans table say MCP and API-key access need a paid plan, while the v3 API page says free-tier accounts can call v3 up to their credits. Taking the stricter reading for the MCP surface, the free tier gives an agent no MCP access (5 of 20). A person signs in through the browser; dynamic client registration and the device flow still end with a human approval (3 of 20). 0 + 15 + 5 + 3 = 23.

Maintenance & community Magic Patterns +29

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.

Magic Patterns 70

Changelog entry on 5 November 2026, the day before this check (30). Entries on twelve dates since 8 August, among them 23 September and 12 to 30 October (20). Closed service with a public changelog, email support within one to two business days, in-app chat and a Slack community. We didn't test them (12 of 15). Not in the official MCP registry (searches for magic-patterns and magicpatterns returned nothing of theirs). Official Claude connector, Cursor plugin and Codex plugin, and no SDKs (5 of 15). No public package or repository to check (3 of 10). 30 + 20 + 12 + 5 + 3 = 70.

Agent ergonomics Framelink MCP for Figma +16

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.

Magic Patterns 67

24 documented tools (15 for 11 to 30), plus 5 back for the read-only endpoint that registers only 12 (20 of 25). Message history pages by 10 and version history by 20 with skip, and file reads take a list of names (14 of 20). Documented status codes, a 402 that leaves reads working and non-blocking validationErrors on design-system writes (15 of 20). No idempotency keys; 409 conflict checks on design-system writes, and annotations couldn't be read on the closed server (10 of 20). create_design needs no parameter and makes a blank scaffold, but there is no official SDK (8 of 15). 20 + 14 + 15 + 10 + 8 = 67.

Transparency & trust Magic Patterns +13

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.

Magic Patterns 60

Closed service under terms of service last updated 1 April 2025 (15). The privacy policy of the same date keeps personal data as long as necessary with no periods. The terms let Magic Patterns train on Free plan inputs and outputs and show Free plan designs publicly, and rule out training on paid plans. The subprocessor list sits in the Trust Center, which wasn't readable (14 of 30). No deprecation policy. v2 is 'being deprecated and will be removed in a future release' with no date, and the terms allow any part of the service to be discontinued at any time (5 of 20). The security page names Render and MongoDB Atlas as hosting, and the full subprocessor list wasn't read (8 of 20). 15 + 14 + 5 + 8 = 42.

Reliability Magic Patterns +7

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.

Magic Patterns 75

Hosted lines, for the MCP server and v3 API. A Statuspage at magicpatterns.statuspage.io with incident history, but its two components are Web Platform and Figma Plugin, with nothing for the API or MCP server (15 of 20). The history page and Atom feed post no incident since 9 January 2026, so the 90 days before this check are clean as far as the page covers (30). The page's /api/ path is disallowed by its robots.txt, so the JSON feeds weren't used. Rate limit published as 1,000 generations per 10 hours per key, with polling no faster than once every 60 seconds (15). No 429, Retry-After or backoff guidance and no idempotency keys. Design-system writes take a baseArtifactId and return 409 on a concurrent change, with re-read-and-retry advice (5 of 15). No SLA found below Enterprise's custom contracts (0). The MCP server and v3 API carry no beta label (10). 15 + 30 + 15 + 5 + 0 + 10 = 75.

Score by category

CategoryWeight this runFramelink MCP for FigmaMagic PatternsEdge
Reliability16%206875Magic Patterns +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28784Framelink MCP for Figma +3
Agent ergonomics13%16.28367Framelink MCP for Figma +16
Security & auth14%17.55555even
Payments & pricing10%12.56023Framelink MCP for Figma +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84170Magic Patterns +29
Transparency & trust7%8.84760Magic Patterns +13
Negative events≤1500
TotalB 66.1/100B 63.4/100

Facts side by side

FactFramelink MCP for FigmaMagic Patterns
KindMCP serverMCP server
VendorFramelink (Graham Lipsman)North Park Labs, Inc. (Magic Patterns)
Hosted endpointno (local only)https://mcp.magicpatterns.com/mcp
Transportsstdio, Streamable HTTPStreamable HTTP, HTTP
AuthTokenOAuth or key
PricingFreeFreemium
x402nono
LicenceMITClosed service under the Magic Patterns terms of service (last updated 1 April 2025)
Tools exposed224
Read-only variant documentednoyes
llms.txtyesyes
MCP registryio.github.GLips/Figma-Context-MCPnot listed
Last release2026-06-182026-11-05
Terms last updatedno document linked2025-04-01
Privacy policy last updatedno document linked2025-04-01
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity16k stars, 162k npm/wknone

Verdicts

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.

Magic Patterns

Agents can create, prompt, read and edit coded prototypes through 24 documented MCP tools or a matching REST API, with a read-only endpoint and 409 conflict checks on writes. MCP access needs a paid seat from $20 a month, OAuth scopes don't narrow access below the user's role, and the status page doesn't track the API or MCP server.

Before you call either

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

Magic Patterns

  1. Use https://mcp.magicpatterns.com/mcp/readonly when the task only reads designs
  2. Call get_design_status before any change and poll it no more than once every 60 seconds
  3. Pass baseArtifactId from get_design_system on writes, and on 409 re-read before retrying
  4. Treat a 402 as out of credits and ask the user; read tools keep working
  5. Send x-mp-agent-name so the user sees which agent made a change

Questions

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

Framelink MCP for Figma scores 66.1 (B) on agent readiness against Magic Patterns's 63.4 (B), and leads in 3 of 7 scored categories. Magic Patterns leads on reliability, maintenance & community and transparency & trust.

Do Framelink MCP for Figma and Magic Patterns need an API key?

Framelink MCP for Figma needs an access token. Magic Patterns takes an API key or an OAuth sign-in.

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

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

Are Framelink MCP for Figma and Magic Patterns open source?

Framelink MCP for Figma is open source (MIT). No open-source release is listed for Magic Patterns.

Other comparisons with Framelink MCP for Figma or Magic Patterns

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.