Head to head · Design files · October 2026 research run

Framelink MCP for Figma vs Paper MCP

Framelink MCP for Figma scores 69.8 (B) on agent readiness against Paper MCP's 38.1 (E), and leads in 5 of 7 scored categories. Paper MCP leads on maintenance & community and transparency & trust. Both do design files.

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

Which one, for what

Framelink MCP for Figma B

Best for Reading a Figma frame into a coding agent to build matching UI.

Ahead on

  • Reliability, 68 against 30
  • Schema & documentation, 87 against 37
  • Agent ergonomics, 83 against 39
  • Security & auth, 55 against 31
  • Payments & pricing, 90 against 30

Also in its favour

  • Open source

Watch for

Last release 0.13.2 on 18 June 2026, and still below 1.0

Paper MCP E

Best for Design teams who want an agent to build and edit screens on a canvas that is HTML and CSS, and to turn frames into code.

Ahead on

  • Maintenance & community, 65 against 41
  • Transparency & trust, 56 against 47

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No published tool schemas or tool list. The Claude extension manifest marks tools as generated by the app

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 Framelink MCP for Figma +60

Framelink MCP for Figma 90

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

Paper MCP 30

No x402, MPP or L402 (0). Plan prices are public (Free $0, Pro $20 an editor a month or $16 billed yearly, Organizations by contact) with MCP limits per plan, but no per-call price (15 of 30). The Free plan includes 100 MCP tool calls a week and unlimited editors. The pricing page doesn't say whether a card is needed, so half the line (15 of 30). A person signs up in a browser and approves the OAuth connection (0). 0+15+15+0 = 30.

Schema & documentation Framelink MCP for Figma +50

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.

Paper MCP 37

The MCP tool definitions are generated by the app (tools_generated: true in the Claude extension manifest) and no page publishes their input schemas. The remote endpoint asks for OAuth before initialize, so no tool list was read. paper.design/openapi.json covers only two unauthenticated website endpoints and says the agent surface is the MCP server, not a REST API (0 of 25). llms.txt with a developer section (10). The MCP docs explain when to use the desktop server or the remote one, and say read tools are safe to always allow while write tools change the file, but the tool descriptions themselves were not readable (8 of 20). Tool names are known only from the ChatGPT plugin's review test cases (open_file, get_basic_info, get_screenshot, create_artboard, write_html, find_nodes, set_text_content, get_computed_styles and others), with no types (3 of 15). Example prompts and a troubleshooting section, with no list of error responses (6 of 15). A monthly dated build log, and plugin versions in the agent-plugins repository (10 of 15). 0+10+8+3+6+10 = 37.

Agent ergonomics Framelink MCP for Figma +44

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.

Paper MCP 39

At least eleven tools are named in the plugin's test cases, and the full count is unknown, with no documented toolsets or read-only subset (12 of 25). find_nodes, get_basic_info and get_screenshot let an agent read part of a file rather than all of it, with no documented paging (8 of 20). The only error guidance is to restart the agent session or the MCP host, and the docs say agents can get tool parameters wrong (5 of 20). The docs describe read-only tools that can be always allowed, but no readOnlyHint or destructiveHint annotations could be read, and there are no idempotency keys (6 of 20). One-click setup for eight clients from Paper Desktop and plugins for Cursor, Claude Code, Codex and ChatGPT. No SDK (8 of 15). 12+8+5+6+8 = 39.

Reliability Framelink MCP for Figma +38

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.

Paper MCP 30

Read with the local-software lines, because the main surface is the stdio server the Paper CLI runs on the owner's machine (paper mcp), with Paper Desktop installed from paper.design/downloads. The Claude extension manifest lists macOS, Windows and Linux, while llms.txt names a macOS download, and no runtime requirements are stated (15 of 20). The app and server are closed, so no public CI or test suite can be seen. The agent-plugins repository has a build workflow that validates plugin manifests only (0). No public issue tracker was found. Support is team@paper.design with a stated reply within 2 business days, plus Discord and Slack (5 of 25). The monthly build log is dated, and the move from the localhost HTTP endpoint to paper mcp kept the old endpoint working while a file is open, with migration steps (10 of 15). No version number is published for the desktop app, and the remote server is early access (0). The remote server and sign-in also depend on Paper's hosted service, which has no status page, and robots.txt disallows /status/. 15+0+5+10+0 = 30.

Security & auth Framelink MCP for Figma +24

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.

Paper MCP 31

The remote server answers 401 with an OAuth protected-resource pointer and signs in with the user's Paper account, and the ChatGPT plugin says the agent can reach only files that account can reach. No scopes or token lifetimes are documented. The local server needs no credential (20 of 30). No read-only mode. The docs rely on the agent client's permission prompts and say the Paper MCP 'can read and write, so make sure you're comfortable with the agent being able to manipulate this specific design file' (5 of 20). Files, comments and pasted or imported content written by others reach the model, and no prompt-injection guidance was found (3 of 15). The canvas shows agent presence and feedback while an agent works, with no audit log or per-call record documented (3 of 15). No security.txt (404), disclosure policy, bug bounty or certification found. SAML and SSO are on the Organizations plan (0 of 20). 20+5+3+3+0 = 31.

Maintenance & community Paper MCP +24

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.

Paper MCP 65

The agent-plugins repository added the remote-MCP plugins for ChatGPT, Codex and Cursor on 7 and 10 November 2026, eight days before this check, and the MCP docs describe the remote server (30). The build log has dated monthly entries for August, September and October 2026 (20). Closed service with a public build log, a support email that states a reply within 2 business days, and Discord and Slack communities. We didn't test support (10 of 15). Not in the official MCP registry (searched for paper and design.paper on 18 November 2026) (0). The plugin repository runs a build workflow on its manifests (5 of 10). 30+20+10+0+5 = 65.

Score by category

CategoryWeightFramelink MCP for FigmaPaper MCPEdge
Reliability16%6830Framelink MCP for Figma +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8737Framelink MCP for Figma +50
Agent ergonomics13%8339Framelink MCP for Figma +44
Security & auth14%5531Framelink MCP for Figma +24
Payments & pricing10%9030Framelink MCP for Figma +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4165Paper MCP +24
Transparency & trust7%4756Paper MCP +9
Negative events≤1500
TotalB 69.8/100E 38.1/100

Facts side by side

FactFramelink MCP for FigmaPaper MCP
KindMCP serverMCP server
VendorFramelink (Graham Lipsman)Paper
Hosted endpointno (local only)https://mcp.paper.design
Transportsstdio, Streamable HTTPstdio, Streamable HTTP
AuthTokenOAuth or key
PricingFreeFreemium
x402nono
LicenceMITnone
Tools exposed2none
Read-only variant documentednoyes
llms.txtyesyes
MCP registryio.github.GLips/Figma-Context-MCPnot listed
Last release2026-06-182026-11-10
Terms last updatedno document linked2026-10-11
Privacy policy last updatedno document linked2026-03-30
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity16k stars, 162k npm/wknone

How the scores have moved

Verdicts

Framelink MCP for Figma

Two compact, typed tools return Figma layout and styles in a token-saving tree format and save image assets, with a read-only hint and a flag that removes the writing tool. There has been no release since 18 June 2026, issues and outside pull requests since July have gone unanswered, and telemetry is on by default.

Paper MCP

Agents get read and write access to a design canvas built on HTML and CSS, one-click setup for eight agent clients and a remote server for cloud agents. Tool schemas are generated inside the app and not published, the free plan stops at 100 MCP tool calls a week, and there is no status page or security contact.

Before you call either

Framelink MCP for Figma

  1. Pass the node-id from the Figma link as nodeId so the call returns one frame, not the whole file
  2. Leave depth unset unless the user asks, as the tool description says
  3. Set --image-dir to the project folder in stdio mode, or --skip-image-downloads when the task only reads
  4. Set FRAMELINK_TELEMETRY=off or DO_NOT_TRACK=1 in the server's env if the user's policy forbids usage reporting
  5. On a 429 from Figma, wait and retry later; the limit is the user's Figma plan, not the server's

Paper MCP

  1. Prefer the desktop server (paper mcp over stdio) when Paper Desktop is open, since it acts on the open file with no cloud round trip
  2. Use https://mcp.paper.design only from cloud agents. The user must sign in to Paper in a browser to finish the OAuth connection
  3. Count calls on a free account, because the free plan allows 100 MCP tool calls a week
  4. If tools fail in a long session, restart the agent session first, as Paper's troubleshooting docs advise
  5. Ask before writing, since the server can change the open design file and has no read-only mode

Questions

Which is better for AI agents, Framelink MCP for Figma or Paper MCP?

Framelink MCP for Figma scores 69.8 (B) on agent readiness against Paper MCP's 38.1 (E), and leads in 5 of 7 scored categories. Paper MCP leads on maintenance & community and transparency & trust.

Do Framelink MCP for Figma and Paper MCP need an API key?

Framelink MCP for Figma needs an access token. Paper MCP takes an API key or an OAuth sign-in.

Can an agent call Framelink MCP for Figma and Paper MCP without installing anything?

Framelink MCP for Figma runs on your own machine, with no hosted endpoint listed. Paper MCP has a hosted endpoint at https://mcp.paper.design.

Are Framelink MCP for Figma and Paper MCP open source?

Framelink MCP for Figma is open source (MIT). No open-source release is listed for Paper MCP.

Other comparisons with Framelink MCP for Figma or Paper 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.