Head to head · Design files · October 2026 research run

Figma API + MCP vs Penpot API + MCP

Figma API + MCP scores 64 (B) on agent readiness against Penpot API + MCP's 35.8 (F), and leads in 5 of 7 scored categories. Penpot API + MCP leads on payments & pricing. 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 44
  • Schema & documentation, 86 against 66
  • Agent ergonomics, 60 against 41
  • Security & auth, 71 against 35
  • Maintenance & community, 84 against 76

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
  • No incidents deducted, where Penpot API + MCP loses 15 points for them

Watch for

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

Penpot API + MCP F

Best for Teams that want design files on their own servers and an agent working alongside a person in the editor.

Ahead on

  • Payments & pricing, 45 against 15

Also in its favour

  • Free to start without a card
  • Open source

Watch for

Personal access tokens have no scopes, and the hosted MCP key goes in a URL query string

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.

Security & auth Figma API + MCP +36

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

Penpot API + MCP 35

Personal access tokens can expire after 30 to 180 days or never and can be deleted at any time, but carry no scopes. The hosted MCP URL still takes its key in the userToken query parameter as the documented setup, so the fixed 10 comes off (10 of 30). OAuth for the MCP server was merged on the develop branch on 28 October and isn't in a release. No read-only mode. execute_code runs arbitrary JavaScript against the plugin API, which can delete shapes, and the MCP docs only advise starting with read-only prompts. The plugin must stay open in the user's tab (5 of 20). Shared files and library content reach the model with no injection guidance (3 of 15). Audit events exist in the codebase and the pricing page's structured data lists audit logs on Enterprise, but we found no operator-facing call log documented (5 of 15). SECURITY.md routes reports through GitHub security advisories with no acknowledgement time (7), and advisories are published in public, 18 Penpot records in the last 12 months (5). No security.txt (404 on 5 November), bug bounty or certification found (12 of 20).

Payments & pricing Penpot API + MCP +30

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.

Penpot API + MCP 45

No machine payment protocol (0). Plan prices are public, Unlimited $7 an editor a month capped at $175 and Enterprise $25 a member, with no per-call price (10 of 20). The cloud Professional plan is free with no card (20). A person signs up and creates the token or MCP key in account settings (0). Self-hosting the community edition is free under MPL-2.0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Reliability Figma API + MCP +20

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

Penpot API + MCP 44

Penpot runs as a cloud service and as self-hosted software, so this is the mean of the two rubrics, rounded half away from zero. Cloud (10). No status page was found on 5 November (0), so no readable incident history (5 of 30). No numeric rate limit, 429 guidance or SLA is published for the cloud. The terms define fair use only as no more than 10 times the median data usage (0, 0, 0). The RPC API is documented and in use, while MCP multi-user mode was described as under development per the 1 October check, not re-read on 5 November (5 of 10). Self-hosted (77). Official Docker images and install guides (20). Backend, frontend, common, end-to-end, exporter, library, MCP, plugins and WASM test workflows run in public GitHub Actions, and the pass state can't be read without github.com, so 15 of 25 by this run's reading (was 20). 706 open issues, labelled with milestones, per the 1 October check, not re-read on 5 November (15 of 25). CHANGES.md records every release, without an API versioning policy (12 of 15). Version 2.18 (15). (10 + 77) / 2 = 43.5, so 44.

Schema & documentation Figma API + MCP +20

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

Penpot API + MCP 66

The integration guide links generated API docs at design.penpot.app/api/_doc, and the backend's page template at 2.18.6 links a Swagger/OpenAPI description, but design.penpot.app's robots.txt disallows /api/ for every crawler, so neither page can be read and neither counts here. Every MCP tool in @penpot/mcp declares a typed zod input schema (read from the source at 2.18.6), which meets the line for MCP (25). No llms.txt (help.penpot.app/llms.txt answered 404 on 5 November). The MCP server's high_level_overview and penpot_api_info tools hand the model its docs instead (3 of 10). RPC docs are generated with little prose. MCP descriptions are long and tell the model to read the overview before execute_code (12 of 20). RPC inputs are typed, but the main MCP tool takes one JavaScript string (9 of 15). A curl example for get-profile. No documented error format, and the integration guide still says 'we do not have any specific documentation for the webhooks yet' (5 of 15). CHANGES.md per release (12 of 15).

Agent ergonomics Figma API + MCP +19

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

Penpot API + MCP 41

Five MCP tools locally and four on the hosted URL in released 2.18.6, though execute_code's description is long. Over RPC, get-file returns a whole file (18 of 25). We found no documented pagination or field selection for RPC commands (8 of 20). No documented error codes for the API (8 of 20). No readOnlyHint, destructiveHint or other annotations on any MCP tool in 2.18.6 or on the develop branch, and no idempotency keys (2 of 20). No official API client. The Plugin API is typed TypeScript (5 of 15).

Maintenance & community Figma API + MCP +8

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

Penpot API + MCP 76

2.18.6 on 2026-11-04 (30). 2.17.1 (17 August), 2.17.2 (27 August), 2.18.0 (23 September), 2.18.1 (1 October), 2.18.2 (5 October), 2.18.3 (6 October), 2.18.4 (23 October), 2.18.5 (26 October) and 2.18.6 inside 90 days, release candidates not counted (20). Issues labelled and given milestones within a day, per the 1 October check, not re-read on 5 November (18 of 25). No readable official MCP registry page and no official API client (0). MCP tests in CI, and MCP and exporter npm dependencies updated on 29 October (8 of 10).

Score by category

CategoryWeightFigma API + MCPPenpot API + MCPEdge
Reliability16%6444Figma API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8666Figma API + MCP +20
Agent ergonomics13%6041Figma API + MCP +19
Security & auth14%7135Figma API + MCP +36
Payments & pricing10%1545Penpot API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8476Figma API + MCP +8
Transparency & trust7%6771Penpot API + MCP +4
Negative events≤150-15
TotalB 64/100F 35.8/100

Facts side by side

FactFigma API + MCPPenpot API + MCP
KindHTTP APIHTTP API
VendorFigmaPenpot (Kaleidos)
Hosted endpointhttps://api.figma.com/v1https://design.penpot.app/api/rpc/command
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyToken
PricingFreemiumFreemium
x402nono
LicenceproprietaryMPL-2.0
Tools exposed415
Read-only variant documentednono
llms.txtyesno
MCP registrycom.figma.mcp/mcpnot listed
Last release2026-10-222026-11-04
Terms last updated2026-03-112025-08-05
Privacy policy last updatedno date given2025-08-05
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity456k npm/wk61k stars
Agent reviews3.5/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate 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.

Penpot API + MCP

MPL-2.0 and self-hostable, with API, webhooks and MCP on the free cloud plan and nine releases since 7 August 2026. Personal access tokens have no scopes, the hosted MCP key goes in a URL query string, and 18 Penpot security records were published in the 12 months to November 2026.

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

Penpot API + MCP

  1. Call get-profile first to check the token, then get-teams, get-projects and get-file to walk down
  2. Ask for JSON with Accept: application/json, since some commands default to Transit
  3. Call high_level_overview and penpot_api_info before execute_code. They tell the model what the plugin API can do
  4. Keep the Penpot tab in the foreground. A backgrounded or frozen tab stalls MCP calls
  5. Give tokens an expiry and run 2.18.6 or later on self-hosted instances. Tokens carry full account access, and 2.18.0 fixed a Critical exporter flaw

Questions

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

Figma API + MCP scores 64 (B) on agent readiness against Penpot API + MCP's 35.8 (F), and leads in 5 of 7 scored categories. Penpot API + MCP leads on payments & pricing.

Do Figma API + MCP and Penpot API + MCP need an API key?

Figma API + MCP takes an API key or an OAuth sign-in. Penpot API + MCP needs an access token.

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

Yes. Figma API + MCP has a hosted endpoint at https://api.figma.com/v1 and Penpot API + MCP at https://design.penpot.app/api/rpc/command.

Are Figma API + MCP and Penpot API + MCP open source?

No open-source release is listed for Figma API + MCP. Penpot API + MCP is open source (MPL-2.0).

Other comparisons with Figma API + MCP or Penpot API + MCP

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.