# Framelink MCP for Figma vs Framer Server API (slim)

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

- Full: https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-framer.md (~5,450 tokens) · this version ~3,430 tokens · JSON https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-framer.json · canonical https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-framer
- 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 Framer Server API's 52.5 (D), and leads in 5 of 7 scored categories. Framer Server API leads on 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
- Framer Server API: D 52.5, rank #984 of 1510 · https://www.anchorterminal.com/tools/framer.min.md
- Framelink MCP for Figma, good for Reading a Figma frame into a coding agent to build matching UI. Ahead on Reliability, 68 against 43; Schema & documentation, 87 against 69; Agent ergonomics, 83 against 47; Security & auth, 55 against 49; Payments & pricing, 60 against 25. Also Runs on your own machine; Open source.
- Framer Server API, good for Coding agents and MCP clients that build or update Framer sites, CMS content and code components. Ahead on Maintenance & community, 77 against 41; Transparency & trust, 75 against 47. Also A hosted endpoint, with nothing to install.

| Category | Framelink MCP for Figma | Framer Server API |
| --- | --- | --- |
| Reliability (16%) | 68 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 69 |
| Agent ergonomics (13%) | 83 | 47 |
| Security & auth (14%) | 55 | 49 |
| Payments & pricing (10%) | 60 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 41 | 77 |
| Transparency & trust (7%) | 47 | 75 |

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

Why the edge:
- Agent ergonomics, Framelink MCP for Figma +36: 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.); Framer Server API 47 (The Server API has no plain HTTP request. A script opens a WebSocket session through the SDK and calls Plugin API methods, and results are whole node or collection objects. Framer MCP gives MCP clients a Streamable HTTP route with no Node or local bridge, but its tool count and size weren't readable without signing in, so this line still reads the Server API (12 of 25). Node queries by type and CMS item access exist, but we found no documented page or field controls (10 of 20). No documented error codes, and a dropped connection can stop a run halfway (8 of 20). Calls aren't transactional, but `@framer/agent` puts every change on a branch, an MCP agent works on a branch when asked, and `publish` makes a preview before `deploy` promotes it. MCP tool annotations weren't readable (10 of 20). JavaScript and TypeScript only, Node 22 or later (7 of 15). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).)
- Maintenance & community, Framer Server API +36: 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.); Framer Server API 77 (Per the 24 October check, not re-read on 4 November, Framer MCP was published on 22 October 2026, and Plugin API v5.1.0 and `framer-api` 5.1.0 on npm on 24 September (30). In the 90 days from 6 August, v5.0.0 (8 September), v5.1.0 (24 September), `@framer/agent` 0.0.47 (15 October, per the 24 October npm reading) and the Framer MCP release (22 October) are four dated entries; v4.1.0 (4 August) has left the window (20). Closed service with a public changelog, an updates page and a community forum. We didn't test support (10 of 15). Presence of Framer MCP in the official MCP registry wasn't established; the 24 October search used the registry's JSON API, which this check doesn't use (0). One official SDK, now at the Plugin API's version (10 of 15). `framer-api` 5.1.0 declares Node 22 or later and two runtime dependencies (7 of 10). Framer's Acceptable Use Policy (version 2.0, effective 9 April 2026) bars robots and other automatic devices from accessing any content hosted by Framer, so framer.com hosts and framerstatus.com weren't re-read on 4 November and this note rests on the 24 October check.)
- Payments & pricing, Framelink MCP for Figma +35: 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.); Framer Server API 25 (No machine payment protocol (0). The Server API is free during beta and Framer says it'll 'likely charge for this API on a per-use basis, with a monthly free allowance', with no price set. The pricing page lists the MCP Server as 'Free during preview' with no later price. Site plans are public (5 of 20). Free on every plan, including the Free site plan, during the Server API beta and the MCP preview (20). A person creates the key in Site Settings, approves `@framer/agent` in a browser or signs in to Framer to approve an MCP client. Dynamic client registration registers the client, not an account (0). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).)
- Transparency & trust, Framer Server API +28: 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.); Framer Server API 75 (Closed service under published terms, version 1.8 effective 16 June 2026, whose definition of the Service excludes Framer APIs. `framer-api` is MIT on npm, and `@framer/agent` 0.0.47 declares no licence (18 of 30). Privacy statement version 1.7 of 12 June 2026 names Framer B.V., gives retention periods (transaction data 7 years, account data up to 2 years after closure) and links a DPA. Its AI line only covers training 'third-party general-purpose AI models' on personal data (22 of 30). Breaking changes are flagged by major version, such as the v4.0.0 package rename and v5.0.0 CMS array fields, with no deprecation policy or notice period. The External Agents page is now labelled legacy and stays supported 'while Framer MCP reaches feature parity', with no end date (8 of 20). Transfer countries are listed in the Trust Center per the privacy statement. We didn't confirm a subprocessor list (10 of 20). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).)
- Reliability, Framelink MCP for Figma +25: 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.); Framer Server API 43 (Per the 24 October check, not re-read on 4 November, Framer runs a Better Stack status page at framerstatus.com with App, Editor, API, Hosting, Sites, Website and Community components, and no component for Framer MCP (20). Its RSS feed showed three incidents in the 90 days to 24 October 2026, analytics collection degraded at a third-party provider for about 1 hour 15 minutes on 12 August, elevated errors in the AI tools for 1 hour 15 minutes on 22 September and the Editor unavailable for 39 minutes on 14 October, with the API component at 100 per cent over 30 days. Minor only. 25 October to 4 November is unread and gets no credit of its own (20 of 30, kept). No rate limits published for the Server API or Framer MCP (0). No 429 or retry guidance. The FAQ says the API 'is not in any way transactional' and scripts must handle partial failures themselves (3 of 15, partial kept). No SLA published. The Enterprise plan lists an 'Uptime guarantee' without published terms (0). The Server API is in open beta and Framer MCP is labelled preview on the pricing page (0 of 10). Framer's Acceptable Use Policy (version 2.0, effective 9 April 2026) bars robots and other automatic devices from accessing any content hosted by Framer, so framer.com hosts and framerstatus.com weren't re-read on 4 November and this note rests on the 24 October check.)
- Schema & documentation, Framelink MCP for Figma +18: Framelink MCP for Figma 87 (Both tools have typed zod input schemas in src/mcp/tools, with regex checks on fileKey, nodeId and fileName (25). docs.framelink.ai serves llms.txt and a Markdown copy of each page (10). The tool reference explains what each tool returns and how the two chain through `imageDownloadArguments`, and the `depth` parameter says not to use it unless the user asks. The `get_figma_data` description itself is one line and says nothing about when not to call it (14 of 20). Required fields and patterns are typed, and `fileName` must end in .png, .svg or .gif, with no enum for output format at call time (13 of 15). Config and request examples in the docs, a documented `Error fetching file:` prefix and purpose-built 403 and 429 messages, but no list of error cases (10 of 15). Semver releases and a public changelog (15). 25 + 10 + 14 + 13 + 10 + 15 = 87.); Framer Server API 69 (No OpenAPI or REST contract. The Server API's contract is the TypeScript types in the `framer-api` SDK over a WebSocket (12 of 25). llms.txt at framer.com, re-read on 24 October (10). The Plugin API reference documents each method, and `@framer/agent` installs skills that tell coding agents how to use it (12 of 20). Typed TypeScript inputs with union types for node and field kinds (12 of 15). Quick-start examples and a REST-wrapper example on GitHub. No error reference found (8 of 15). A dated changelog with semver and breaking changes flagged, v4.1.0 on 4 August, v5.0.0 on 8 September and v5.1.0 on 24 September 2026, and a dated updates page that announced Framer MCP on 22 October (15). Framer doesn't publish Framer MCP's tool definitions and listing them needs an OAuth sign-in, so this score still reads the Server API. Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).)