# Framelink MCP for Figma vs Magic Patterns (slim)

> Framelink MCP for Figma scores 66.1 (B) to Magic Patterns's 63.4 (B) for design files. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-magic-patterns.md (~4,450 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-magic-patterns.json · canonical https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-magic-patterns
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Framelink MCP for Figma: B 66.1, rank #387 of 1510 · https://www.anchorterminal.com/tools/framelink-figma-mcp.min.md
- Magic Patterns: B 63.4, rank #519 of 1510 · https://www.anchorterminal.com/tools/magic-patterns.min.md
- Framelink MCP for Figma, good 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 Runs on your own machine; Open source.
- Magic Patterns, good 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 A hosted endpoint, with nothing to install.

| Category | Framelink MCP for Figma | Magic Patterns |
| --- | --- | --- |
| Reliability (16%) | 68 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 84 |
| Agent ergonomics (13%) | 83 | 67 |
| Security & auth (14%) | 55 | 55 |
| Payments & pricing (10%) | 60 | 23 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 41 | 70 |
| Transparency & trust (7%) | 47 | 60 |

| Fact (where they differ) | Framelink MCP for Figma | Magic Patterns |
| --- | --- | --- |
| Vendor | Framelink (Graham Lipsman) | North Park Labs, Inc. (Magic Patterns) |
| Hosted endpoint | no (local only) | `https://mcp.magicpatterns.com/mcp` |
| Transports | stdio, Streamable HTTP | Streamable HTTP, HTTP |
| Auth | Token | OAuth or key |
| Pricing | Free | Freemium |
| Licence | MIT | Closed service under the Magic Patterns terms of service (last updated 1 April 2025) |
| Tools exposed | 2 | 24 |
| Read-only variant documented | no | yes |
| MCP registry | `io.github.GLips/Figma-Context-MCP` | not listed |
| Last release | 2026-06-18 | 2026-11-05 |
| Terms last updated | no document linked | 2025-04-01 |
| Privacy policy last updated | no document linked | 2025-04-01 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 16k stars, 162k npm/wk | none |

Why the edge:
- 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.)