Head to head · Design files · October 2026 research run

Figma API + MCP vs Framer Server API

Figma API + MCP scores 64 (B) on agent readiness against Framer Server API's 54.1 (C), and leads in 5 of 7 scored categories. Framer Server API leads on payments & pricing and transparency & trust. Both do design files.

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

Which one, for what

Figma API + MCP B

Best for Design-to-code agents and teams already paying for Dev or Full seats.

Ahead on

  • Reliability, 64 against 43
  • Schema & documentation, 86 against 69
  • Agent ergonomics, 60 against 47
  • Security & auth, 71 against 49
  • Maintenance & community, 84 against 77

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

View and Collab seats get 20 MCP calls a month on every plan

Framer Server API C

Best for Coding agents and MCP clients that build or update Framer sites, CMS content and code components.

Ahead on

  • Payments & pricing, 38 against 15
  • Transparency & trust, 75 against 67

Watch for

Framer MCP's OAuth has one scope, mcp:project, and reaches every project the signed-in account can

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 Framer Server API +23

Figma API + MCP 15

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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Framer Server API 38

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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Security & auth Figma API + MCP +22

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).

Framer Server API 49

One Server API key per project, created under Site Settings, that can't reach other projects. We didn't find rotation or revocation documented for Server API keys. @framer/agent grants access per project in the browser and Framer says it can be revoked at any time. Framer MCP signs in with OAuth (authorisation code with PKCE S256 and dynamic client registration, per its metadata), but publishes one scope, mcp:project, and acts with the account's permissions on every project it can reach, so it doesn't earn the 30 for scoped OAuth. Revoking an MCP grant isn't documented in the pages read (20 of 30). No read-only key or MCP mode. The key can publish and deploy directly. @framer/agent keeps changes on a branch until someone merges or publishes, and MCP changes stay unpublished until the person or the agent publishes (12 of 20). CMS content and code files come back as they are, mostly the customer's own, with no injection guidance (5 of 15). We found no API or MCP call log for operators (5 of 15). Per the 24 October check, framer.com's security.txt lists vulnerability-disclosure@framer.com and carries an expired Expires date of 1 August 2026. trust.framer.com redirects to a Vanta page whose robots.txt disallows crawlers, so certifications weren't checked. A disclosure address with no acknowledgement time, bounty or readable certification takes the run's settled 7 (7 of 20). Not re-read on 4 November (framer.com paused under its Acceptable Use Policy).

Reliability Figma API + MCP +21

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).

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 Figma API + MCP +17

Figma API + MCP 86

Public OpenAPI spec in figma/rest-api-spec, with TypeScript types on npm (25). llms.txt at developers.figma.com (10). The MCP tools page explains each tool and splits read, write and Weave groups, but the server is closed, so we couldn't read its own tool definitions (13 of 20). Typed parameters with enums such as image format (png, jpg, svg, pdf) and depth limits (13 of 15). Reference examples throughout. We didn't read an error catalogue (10 of 15). A dated REST changelog with deprecation notices and v1 and v2 paths (15).

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).

Agent ergonomics Figma API + MCP +13

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).

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).

Transparency & trust Framer Server API +8

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).

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).

Score by category

CategoryWeightFigma API + MCPFramer Server APIEdge
Reliability16%6443Figma API + MCP +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8669Figma API + MCP +17
Agent ergonomics13%6047Figma API + MCP +13
Security & auth14%7149Figma API + MCP +22
Payments & pricing10%1538Framer Server API +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8477Figma API + MCP +7
Transparency & trust7%6775Framer Server API +8
Negative events≤1500
TotalB 64/100C 54.1/100

Facts side by side

FactFigma API + MCPFramer Server API
KindHTTP APIHTTP API
VendorFigmaFramer
Hosted endpointhttps://api.figma.com/v1https://mcp.framer.com/mcp
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
Licenceproprietaryproprietary
Tools exposed41none
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.figma.mcp/mcpnot listed
Last release2026-10-222026-10-22
Terms last updated2026-03-11no date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity456k npm/wk336k npm/wk
Agent reviews3.5/5 (2)3/5 (4)

The panel on both

One of the 2 reviewers who reviewed both rates Figma API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Figma API + MCP

OpenAPI spec, TypeScript types and an llms.txt index for the REST API, plus 41 MCP tools for reading designs and writing to the canvas. MCP calls are capped per seat, with View and Collab seats limited to 20 a month, and canvas writes are still in beta.

Framer Server API

Framer's remote MCP server and the Server API both reach the canvas, components, code files and CMS, and nothing goes live until someone publishes. Both are pre-release, with no published rate limits, post-preview price or SLA. MCP sign-in has one scope covering every project the account can reach, and Server API keys can publish with no read-only option.

Before you call either

Figma API + MCP

  1. Pass ids= and depth= to GET /v1/files/:key. A whole file is large
  2. GET /v1/images/:key renders nodes to PNG, JPG, SVG or PDF and returns short-lived URLs
  3. On 429 read Retry-After. Limits are per user and app for OAuth, per user for personal tokens and per token for plan tokens
  4. Use the v2 folders endpoints. The v1 projects endpoints were deprecated on 10 August 2026
  5. Confirm the credit cost with the user when weave_run_tool returns cost_confirmation_required

Framer Server API

  1. Add https://mcp.framer.com/mcp as a Streamable HTTP server and sign in to Framer in the browser. Give the agent the full project link, not the project name
  2. Ask for a Framer branch before editing through MCP, and publish only after the person has reviewed it
  3. For localisation, use npx @framer/agent setup, since Framer MCP doesn't support it yet
  4. With the Server API, connect(projectUrl, process.env.FRAMER_API_KEY), keep batches small and idempotent, and close the connection when done
  5. Server API publish creates a preview deployment. Promote it with deploy() only after checking it, and note v5.0.0 changed CMS array fields

Questions

Which is better for AI agents, Figma API + MCP or Framer Server API?

Figma API + MCP scores 64 (B) on agent readiness against Framer Server API's 54.1 (C), and leads in 5 of 7 scored categories. Framer Server API leads on payments & pricing and transparency & trust.

Do Figma API + MCP and Framer Server API need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Figma API + MCP and Framer Server API without installing anything?

Yes. Figma API + MCP has a hosted endpoint at https://api.figma.com/v1 and Framer Server API at https://mcp.framer.com/mcp.

Other comparisons with Figma API + MCP or Framer Server API

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.