# Figma API + MCP vs Framelink MCP for Figma (slim)

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

- Full: https://www.anchorterminal.com/compare/figma-mcp-vs-framelink-figma-mcp.md (~4,500 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/figma-mcp-vs-framelink-figma-mcp.json · canonical https://www.anchorterminal.com/compare/figma-mcp-vs-framelink-figma-mcp
- 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 Figma API + MCP's 63.4 (B), and leads in 4 of 7 scored categories. Figma API + MCP leads on security & auth, maintenance & community and transparency & trust. Both do design files.

- Figma API + MCP: B 63.4, rank #515 of 1486 · https://www.anchorterminal.com/tools/figma-mcp.min.md
- Framelink MCP for Figma: B 66.1, rank #386 of 1486 · https://www.anchorterminal.com/tools/framelink-figma-mcp.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 41; Transparency & trust, 67 against 47. Also A hosted endpoint, with nothing to install.
- Framelink MCP for Figma, good for Reading a Figma frame into a coding agent to build matching UI. Ahead on Agent ergonomics, 83 against 60; Payments & pricing, 60 against 10. Also Runs on your own machine; Open source.

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

| Fact (where they differ) | Figma API + MCP | Framelink MCP for Figma |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Figma | Framelink (Graham Lipsman) |
| Hosted endpoint | `https://api.figma.com/v1` | no (local only) |
| Transports | HTTP, Streamable HTTP | stdio, Streamable HTTP |
| Auth | OAuth or key | Token |
| Pricing | Freemium | Free |
| Licence | proprietary | MIT |
| Tools exposed | 41 | 2 |
| MCP registry | `com.figma.mcp/mcp` | `io.github.GLips/Figma-Context-MCP` |
| Last release | 2026-10-22 | 2026-06-18 |
| Terms last updated | 2026-03-11 | no document linked |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | yes, with an opt-out | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 456k npm/wk | 16k stars, 162k npm/wk |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Payments & pricing, Framelink MCP for Figma +50: 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).); 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.)
- Maintenance & community, Figma API + MCP +43: 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).); 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 +23: 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).); 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, Figma API + MCP +20: 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).); 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.)
- 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).); 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.)