Official MCPGenerally availablePublishes llms.txt

Figma MCP Server

Capable, but you pay before an agent can act.

Best design-to-code context available, and the clearest example of seat-based metering: the protocol is not the limit, your Figma seat is.

Design

3.5/5

Agent-readiness

Good overall

Weighted across four pillars

Reach4.5

Cost1.5

Control2.5

Trust5

Official MCP Server

Visit Website

0 views · 0 clicks

What an agent can do here

Official Figma MCP server gives agents design context and write access to files — but tool calls are metered by seat, and Starter accounts get about six per month.

Action depth: Core write
Hosting: Vendor-hosted
Auth: OAuth
Unattended: Needs a human
Blast radius: Medium

What it costs to let an agent act

Paid planHard cap

Needs a Dev or Full seat on a paid plan (Professional/Organization/Enterprise). Starter plans, or View/Collab seats on paid plans, are capped at ~6 tool calls per month. Paid Dev/Full seats get Tier-1 REST limits (e.g. 200 calls/day, 10/min on Education). Desktop server also requires the desktop app with Dev Mode enabled.

Hard cap — the protocol is not the limit here, your plan is.

How the score breaks down

Every factor below is scored by a fixed rubric, not by opinion — so two tools with the same shape always get the same number.

Reach

Excellent4.5/5

Can an agent actually do the job?

MCP serverFirst-party2/2
Action depthCore write1/1.5
HostingVendor-hosted1/1
Fallback pathPublic API0.5/0.5

Cost

Limited1.5/5

What does it cost to let the agent act?

Plan requiredPaid plan1.5/3
Usage meteringHard cap0/2

Control

Workable2.5/5

Can I let it run unattended?

Permission scopingPartial scopes1/1.5
Unattended authHuman OAuth0/1.5
Blast radiusMedium1/1.5
Auth frictionOAuth0.5/0.5

Trust

Excellent5/5

Will this still work next month?

MaintainerVendor2/2
MaturityGenerally available1.5/1.5
Research confidenceHigh1/1
FreshnessVerified 2d ago0.5/0.5

Figma vs other design tools

Sorted by overall score. Filter and sort the full category →

Design MCP servers compared
Tool	Overall	Reach	Cost	Control	Trust	Cost to act	Can do	Risk
WebflowExcellentStrongest agent story among site builders: official, open-source, OAuth, and element/component/style writes no longer need a human in the Designer.	4.5	4.5	5	4	5	FreeUnmetered	Core writeHeadless	Mediumblast radius
CanvaGoodConnecting is free; doing anything useful is not. Built on the Connect API and converging on its full surface over time.	4	4.5	3.5	2.5	5	Paid planUnmetered	Core writeNeeds a human	Mediumblast radius
Adobe PhotoshopGoodOfficial connector is account-scoped and generative-leaning; deep layer-level control still means a community UXP bridge and your own setup.	3.5	4	3.5	2.5	4	Paid planUnmetered	Shallow writeNeeds a human	Mediumblast radius
FigmaGoodBest design-to-code context available, and the clearest example of seat-based metering: the protocol is not the limit, your Figma seat is.	3.5	4.5	1.5	2.5	5	Paid planHard cap	Core writeNeeds a human	Mediumblast radius
PenpotWorkableThe no-paywall option: community server, self-hosted, unmetered. Read-focused today, and nobody at Penpot is maintaining the server for you.	3	2	5	3.5	2.5	FreeUnmetered	Read onlyHeadless	Lowblast radius
FramerWorkableThe weaker half of the Framer-vs-Webflow comparison for agents: no REST, no first-party server, and MCP only via third-party wrappers around a beta WebSocket API.	2.5	2.5	3.5	1.5	2.5	Paid planUnmetered	Shallow writeNeeds a human	Mediumblast radius

Reviews

Write a review

Please log in to leave a review

Setup

How we know

Last verified: 2026-09-29 · 2d ago
Research confidence: high
Maturity: Generally available

Users report seat upgrades not immediately lifting limits — worth a known-issues note on the listing page.

Sources

Spotted something wrong? Send a correction — vendor corrections are applied first.

Official MCP

Visit Website