# Figma API + MCP vs Magic Patterns (slim)

> Figma and Magic Patterns score within a point of each other for design files, 63.4 and 63.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/figma-mcp-vs-magic-patterns.md (~5,050 tokens) · this version ~3,230 tokens · JSON https://www.anchorterminal.com/compare/figma-mcp-vs-magic-patterns.json · canonical https://www.anchorterminal.com/compare/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)

Figma API + MCP and Magic Patterns score within a point of each other on agent readiness, 63.4 (B) and 63.4 (B). Magic Patterns leads on reliability, agent ergonomics and payments & pricing. Both do design files.

- Figma API + MCP: B 63.4, rank #517 of 1510 · https://www.anchorterminal.com/tools/figma-mcp.min.md
- Magic Patterns: B 63.4, rank #519 of 1510 · https://www.anchorterminal.com/tools/magic-patterns.min.md
- Figma API + MCP, good for Design-to-code agents and teams already paying for Dev or Full seats. Ahead on Security & auth, 71 against 55; Maintenance & community, 84 against 70; Transparency & trust, 67 against 60.
- 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 64; Agent ergonomics, 67 against 60; Payments & pricing, 23 against 10.

| Category | Figma API + MCP | Magic Patterns |
| --- | --- | --- |
| Reliability (16%) | 64 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 84 |
| Agent ergonomics (13%) | 60 | 67 |
| Security & auth (14%) | 71 | 55 |
| Payments & pricing (10%) | 10 | 23 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 84 | 70 |
| Transparency & trust (7%) | 67 | 60 |

| Fact (where they differ) | Figma API + MCP | Magic Patterns |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Figma | North Park Labs, Inc. (Magic Patterns) |
| Hosted endpoint | `https://api.figma.com/v1` | `https://mcp.magicpatterns.com/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, HTTP |
| Licence | proprietary | Closed service under the Magic Patterns terms of service (last updated 1 April 2025) |
| Tools exposed | 41 | 24 |
| Read-only variant documented | no | yes |
| MCP registry | `com.figma.mcp/mcp` | not listed |
| Last release | 2026-10-22 | 2026-11-05 |
| Terms last updated | 2026-03-11 | 2025-04-01 |
| Privacy policy last updated | no date given | 2025-04-01 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 456k npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Security & auth, Figma API + MCP +16: Figma API + MCP 71 (OAuth 2 with per-resource scopes such as `file_content:read` and `file_comments:write` (the 22 October Teams endpoints add `teams:write`, `folders:write` and `team_members:write`), scoped personal access tokens, and plan access tokens with resource allowlists and expiry of up to a year. The MCP server signs in with OAuth and only catalogue-listed clients can connect (30). Read-only scopes give least privilege on REST. The MCP server has no documented read-only mode, and canvas writes such as `use_figma` run without a confirmation step (13 of 20). File content, layer names and comments written by collaborators reach the model as they are, and we found no prompt-injection guidance (3 of 15). Activity logs and an AI usage API for Enterprise (12 of 15). Figma runs a bug bounty programme on HackerOne (hackerone.com/figma, "Figma - Bug Bounty Program"). www.figma.com's robots.txt disallows our crawler on every path, so the security page's certifications read on 1 October are struck and security.txt stays unread. Graded as meta-marketing-api's 13 (bounty route confirmed elsewhere, the vendor's own security pages unread) (13 of 20).); Magic Patterns 55 (OAuth 2.1 with PKCE S256, dynamic registration and a device flow, issued by oauth.magicpatterns.com with WorkOS keys. Scopes are openid, email, profile and offline_access only, so a token carries the user's whole workspace role. API keys are shown once, with no scopes, expiry or rotation documented (22 of 30). The read-only endpoint doesn't register the 13 tools that create, change or publish. There is no confirmation step on the write endpoint (14 of 20). Tools return design code and chat history that collaborators wrote, and no prompt-injection guidance was found (3 of 15). `x-mp-agent-name` attributes changes in the UI, and audit logs come with Enterprise only (8 of 15). The security page describes encryption, logging and the Render and MongoDB Atlas setup and points to SOC 2 reports in a Trust Center drawn by script, which wasn't read. No security.txt, disclosure policy or bug bounty found (8 of 20). 22 + 14 + 3 + 8 + 8 = 55.)
- Maintenance & community, Figma API + MCP +14: Figma API + MCP 84 (REST changelog entry on 22 October 2026 (Teams, folder creation, file duplication and invite endpoints for Enterprise) (30). REST changelog entries on 10 August, 17 September and 22 October (20). Closed service with a public changelog and support. We didn't test support (12 of 15). com.figma.mcp/mcp is in the official registry under a DNS-verified namespace, latest 1.0.3 (15). @figma/rest-api-spec and Code Connect are maintained on npm. We didn't audit their dependencies (7 of 10).); 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.)
- Payments & pricing, Magic Patterns +13: Figma API + MCP 10 (No x402 or other machine payment (0). Seat prices sit on www.figma.com/pricing, whose robots.txt disallows our crawler, so the 30 September reading is struck. MCP calls and the coming usage-based write tools have no per-call price on the developer pages (0 of 20). The help centre says "The Starter plan is a free Figma plan", but no readable page states whether a card is needed, so half the line, as anchor-browser's free tier with no card rule (10 of 20). View and Collab seats get 20 MCP calls a month. A person signs up in a browser and approves OAuth, and only catalogue clients can connect (0).); 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.)
- Reliability, Magic Patterns +11: Figma API + MCP 64 (Statuspage at status.figma.com with history, read from its Atom feed (20). From 3 August to 1 November the feed posts four incidents. The 27 September "Service disruption" ("Figma Services are degraded or unavailable because of failures with AWS and other dependencies", 01:04 to 02:32 UTC) hit every service and reads as a major. The 26 August "Figma MCP Disruption" (10:14 to about 14:03 UTC) kept "some Codex and ChatGPT users" from seeing MCP tools, so it's partial and minor. The 13 October Figma agent and Make errors and the 30 October Sites publishing problem don't touch the REST API or the MCP server. The 27 July file-editing incident left the window. One major (10). Published limits for REST by tier, seat and plan, and for MCP by seat (Full and Dev up to 200 calls a day and 10 a minute on Professional, 15 on Organization, 600 a day and 20 a minute on Enterprise; View and Collab 20 a month on every plan) (15). REST 429s carry `Retry-After`, `X-Figma-Plan-Tier` and `X-Figma-Rate-Limit-Type`. No idempotency guidance for comment or variable writes (12 of 15). No SLA found on the developer pages (0). REST is GA, and writing to the canvas is still "free during the beta period" on the MCP introduction (7 of 10).); 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.)
- Agent ergonomics, Magic Patterns +7: Figma API + MCP 60 (REST file reads can be cut down with `ids` and `depth`. The MCP server lists 41 tools (18 read, 14 write, 9 Weave; 35 on 1 October), with some remote-only and others desktop-only, and we found no toolsets or read-only subset (15 of 25). Cursor pagination on comments, versions and folders (16 of 20). REST errors carry a status and message (13 of 20). We couldn't confirm readOnlyHint or destructiveHint on the closed MCP server, and REST writes have no idempotency keys. `weave_run_tool` stops with `cost_confirmation_required` until the caller acknowledges the credit cost (8 of 20). TypeScript types for REST and the Code Connect CLI, but no official REST client in two languages (8 of 15).); 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, Figma API + MCP +7: Figma API + MCP 67 (Closed service. The terms sit on www.figma.com, whose robots.txt disallows our crawler; held at 15 as whatsapp-cloud-api's licence line was with its terms unread (15). The privacy policy and sub-processor list read on 1 October are on the same host and are struck. The help centre's content-training article says training is on by default for Starter and Professional teams and off for Organization and Enterprise, that third-party model providers must delete inputs and outputs after processing, and that Figma upholds its data processing agreements, but it gives no retention period and has no second readable document to agree with (12 of 30). Dated deprecation notices on the developer changelog, such as the v1 projects endpoints on 10 August 2026, but no removal dates (13 of 20). The help article links a sub-processor list for Figma AI that we can't read and mentions data residency commitments without naming locations (5 of 20).); 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.)