Canvashand
Start free trial
All guides

Canvashand vs the official Figma MCP server

Canvashand vs Figma's official MCP server for AI agents: call limits, seats, tools, multi-file work and Figma to code, with sourced Figma figures.

We make Canvashand, so read this as a vendor comparison. Canvashand and the official Figma MCP server both connect Claude Code, Cursor, Codex, and other MCP clients to Figma, and both can write to the canvas. The short answer: pick Figma MCP for Code Connect and a hosted server with nothing to install; pick Canvashand when your agents make many reads, work in several files at once, or write to the canvas in any file you can already edit. This guide is for developers choosing one for agent work. Every Figma figure below was re-checked against Figma's docs on 2026-10-07 and links its source at the end. Figma can change its limits, so check the source before you rely on a number.

At a glance

Figma MCP Canvashand
Price Included with Figma access. Write to canvas is free during its beta and is expected to become usage-based. Free includes 2,000 calls a month. Pro is $6.99 a month or $69.99 a year with unlimited calls. Every Pro plan starts with a 7-day free trial.
Call limits Read tools are metered: up to 20 calls a month on View and Collab seats and on Starter; 200 a day on Professional and Organization Dev and Full seats; 600 a day on Enterprise. Write tools are exempt. Free: 2,000 calls a month across every tool. Pro: unlimited, no per-day or per-minute throttle.
Seat or token needed OAuth sign-in. Writing to a file needs a Full seat. No Dev seat and no Figma API token. The plugin runs in any file you can edit.
Tools Figma's docs list 18 read tools and 12 write tools, plus Weave workflow tools. 99 granular read and write tools.
Several files at once The remote server takes a link to a frame or layer on each call. Every open file connects to one local server, and each call can name a fileId.
Undo Figma's own undo and version history apply. The docs' tool list has no rollback tool. Change sessions per file: rollback deletes what a session created; an explicit begin_change_session also saves a version-history checkpoint for edits.
Figma to code Design context for a frame or layer, plus Code Connect. The agent reads nodes by ID, builds with your repository's components, and checks the result with a screenshot diff.
Where design data goes The remote server is hosted by Figma. The desktop server runs through the Figma desktop app. The plugin talks to a server on 127.0.0.1.

Where the Figma MCP server is the better fit

Code Connect. Figma's server can include real implementation details from your codebase in its output when your design system components are mapped with Code Connect.

First-party support. It is built and maintained by Figma. When the product, the file format, or the plans change, Figma's server changes with them.

No extra install. The remote server connects to a hosted endpoint, with no desktop app and no plugin to run. Canvashand needs its plugin open in each file.

Enterprise headroom. Full and Dev seats on Enterprise get the highest documented allowance, 600 read calls a day, and the docs say Figma may change limits.

If your team already pays for Full seats, mostly reads designs, and stays under those limits, the official server is a sound default.

Where Canvashand is the better fit

No caps

Figma MCP meters read tools per seat and plan. A View or Collab seat gets up to 20 calls a month, and a Professional Dev or Full seat gets 200 a day. Canvashand Free includes 2,000 calls a month, and Pro is unlimited. A loop that reads every frame of a large flow adds up quickly against those numbers. Figma MCP rate limits by seat and plan has the full table and what to do when you hit one.

No Dev seat, no API token

Canvashand works through its plugin in any file you can edit. It does not use the Figma REST API, so there is no personal access token to create and no REST quota to hit, which matters if you have used servers built on that API. Figma's own MCP server signs in with OAuth instead. Canvashand does not grant edit rights a seat lacks: it works only where you can already edit, and it needs no Dev seat upgrade to get read volume, since Pro is unlimited. Figma's docs say writing to a file through its server needs a Full seat.

99 granular tools

Canvashand exposes 99 tools across nodes, pages, styles, variables, components, prototypes, bulk edits, and exports. That means an agent can call set_auto_layout on one frame or batch_rename_nodes across a page instead of describing every change in one general-purpose write call. Figma's set is smaller and more general, and use_figma is its main write tool.

Built for agents

Open the plugin in several files and each connects to the same local server. Three subagents can build three files at once, each passing its own fileId. Each file keeps its own change sessions and rollback journal, so one agent's rollback never touches another file's work (how multi-file agents work). A design plan and audit step refuses to call a job done while screens, states, or flows are uncovered, and canvashand setup configures 12 AI clients in one command (step-by-step for Claude Code and Cursor).

Local

The plugin talks to the Canvashand server on 127.0.0.1, and the server hands results to your AI client. Design data never goes to the Canvashand cloud, which only handles sign-in, billing, call counts, and client versions. If your agent work touches unreleased product designs, you decide where the data goes after it reaches your client.

Figma link to code that matches

Paste a link to a screen or a flow board and ask your agent to build it. The agent turns the link's node-id into node IDs, reads those nodes, and builds with your repository's components and tokens. The linked file must be open in Figma desktop with the plugin running. Figma's remote server also works from links; Canvashand's bundled skill runs a screenshot-diff loop for you, and Pro has no read cap on large flows.

Which one should you use?

  • Pick Figma MCP if you rely on Code Connect, want a first-party hosted server with nothing to install, or read designs a few times a day.
  • Pick Canvashand if your agents loop over many reads, run agents in several files in parallel and want per-file change sessions and rollback, or want canvas writes through a plugin in any file you can already edit.
  • Use both if you want each strength. Two MCP servers with different names can sit in one client, so Figma MCP can supply Code Connect context while Canvashand does the canvas edits.

If your goal is code from a design, read Turn a Figma link into code that matches. Start free with 2,000 calls a month on the setup page, or compare plans on the pricing page.

Sources

Figma is a trademark of Figma, Inc. Canvashand is independent and not affiliated with Figma, Inc.