Deskhand puts Claude on the canvas you already have open. It reads your components, styles and variables, builds with them, and reads the result back before it tells you it is done. Your file stays yours.
14 days free. No card, no key. Then £5 a month or £50 a year.
Claude is asked for the Yearly pricing card. Deskhand runs figma_execute, builds the card on the canvas from the file’s Button and Pill components, reads each write back, screenshots the frame and reviews it: lint clean.
›Build the Yearly pricing card from our components.
Pricing card · YearlySave £10 a yearYearly£50a year£4.17 a month, billed yearly. £10 less than paying monthly.Subscribe yearlyButton · Primary / Site lgBoth include:All 113 tools, every profileScreenshots, review and compareEvery update
Screenshot savedReview: lint clean
Deskhandv1.0.0
ConnectedDeskHand · Design:3056 12 ms
StatusActivitySettings
Running figma_execute3.2 s
Building Pricing card · 12 of 20 nodesCancel
ActivityClear
Waiting for the first command.
2 snapshots · Lint pendingTrial · 9 days left
Works withClaude CodeClaude DesktopFigmaFigJam
Deskhand
What it does
Builtwithyourcomponents.Checkedonyourcanvas.
Claude already writes good screens. The problem is where they land: a flat image, a new file, or a frame full of shapes that look like your buttons. Deskhand puts the work in your file, made from the parts that are already there.
Deskhand
Builds with your components
Claude searches your components, styles and variables before it draws anything. Buttons are instances of your Button. Colours are your tokens, bound, not pasted hex.
Deskhand
Reads back every write
Every write tool reads the result back and reports what Figma stored. A write that did not take returns an error, not a success. What Claude says it did is what is on the canvas.
Deskhand
Screenshots, reviews, comparisons
Claude renders the frame, reviews the screen against the design rules, and compares it to a reference with a mismatch percentage per quadrant. It fixes what it finds, then checks again.
Deskhand flows
OnboardingOpen the fileRun the pluginPick a serverBuild
Deskhandv1.0.0
ConnectedDeskhand flows · FigJam:3056 12 ms
StatusActivitySettings
ActivityClear
figma_create_section211 ms
figma_create_shape_with_text453 ms
figma_create_connector211 ms
Profile figjam · 109 toolsTrial · 9 days left
Deskhand
FigJam too
Stickies, shapes with text, connectors, tables and code blocks. A flowchart arrives as connected shapes in a section, not a picture of one. 109 tools in the figjam profile.
DeskHand
SubscribePricing · YearlyCheckout
DesignPrototype
InteractionsOn clickNavigate to CheckoutSmart animate · 300 ms
Deskhandv1.0.0
ConnectedDeskHand · Design:3056 12 ms
StatusActivitySettings
ActivityClear
figma_add_reaction211 ms
figma_screenshot1.2 s
Deskhand
Prototypes
Reactions, triggers, transitions and flow starting points, written and read back in Figma Design files.
DeskHandDesignDev Mode
Pricing card
InspectPlugins
Deskhandv1.0.0
ConnectedDeskHand · Dev Mode:3056 12 ms
StatusActivitySettings
ConnectionLive
FileDeskHand
EditorDev Mode read-only
Port3056
Sessionfigma-mcp-bridge
Uptime2 h 14 m
Serverv1.0.0
Profile all · 113 toolsSnapshots on
Deskhand
Dev Mode
Open a file in Dev Mode and Deskhand reads, searches and exports. It does not edit, because Figma will not let it, and it says so instead of pretending.
How it works
Onecommand.Foursteps.
Install, connect, build, verify. The whole loop runs on your machine, and every step reads back what it did.
01Install
One command. It copies Deskhand into ~/.deskhand, registers it with Claude Code, Claude Desktop or both, and asks for a licence key. Press Enter for the 14-day trial.
Needs Node.js 18 or newer, the Figma desktop app, and Claude Code or Claude Desktop.
$npx deskhand@latest setup
02Connect
In Figma: Plugins, Development, Import plugin from manifest, then run Deskhand. The panel finds the server on port 3055 by itself and shows Connected with your file’s name. Four steps from setup to Connected.
03Build
Ask Claude for a screen, a component set, a flowchart. It reads your file first, builds with what it finds, and keeps responses compact so a session does not burn tokens on readbacks it does not need.
04Verify
Claude screenshots the frame, runs the review, and compares it to your reference. Then it fixes what it found and checks again. You see the canvas, not a promise.
Tools and profiles
113tools.Loadonlytheonesyouuse.
The tools list a session loads on connect is measured by the test suite under a 64 KB ceiling, so the whole list fits in one request. Profiles hide what you are not using today. Responses are compact and paged; anything over 32 KB goes to disk with a preview.
94
tools
design
Figma Design: pages, nodes, auto layout, text, styles, variables, components and variants, images, exports, screenshots, review and compare, prototype reactions, Plugin API scripts.
109
tools
figjam
Everything in design, plus stickies, shapes with text, connectors, tables and code blocks for FigJam.
113
tools
63 KB
tools list
all
Every tool, including the two licence tools. The one to pick when you move between Figma and FigJam in a day.
Change the profile with DESKHAND_PROFILE=design|figjam|all. Setup defaults to design.
Runs on your machine. Nothing leaves it.
The server runs on your Mac. The plugin talks to it over localhost. No design data goes to a relay, a cloud, or Deskhand. Two things do leave: a licence check to Polar, and the plugin’s check with the npm registry for a newer version. Lose the connection and Deskhand keeps working for 7 days on its last licence check, warns after that, and stops at 30.
0113
tools
063 KB
tools list
00
relays
07 days
offline
Pricing
14daysfree.Nocard,nokey.
Install, run the plugin, start working. The trial starts the first time you run Deskhand. When it ends, one subscription keeps reads and writes going. Screenshots, reviews and comparisons are on every subscription, because checking its own work is the point.
The server and the Figma plugin both run on your computer and talk over localhost. Design data does not go through a Deskhand server. Deskhand contacts Polar to check your licence key, and the plugin contacts the npm registry to check for a newer version.
Does it use my Claude subscription?
Yes. Deskhand is an MCP server, so Claude Code or Claude Desktop does the thinking on whatever Claude plan you already have. Deskhand charges nothing per token and nothing per call.
Do I need a Figma API key or a paid Figma seat for it?
No. Deskhand works through a plugin you import into the Figma desktop app, so there is no API key and no per-seat metering. Any Figma plan that lets you run development plugins works.
Does it work offline?
Yes. Deskhand caches the result of its last licence check. It works for 7 days after that check, warns after day 7, and stops at 30 days until it can reach the licence server again.
Can I use it in FigJam?
Yes. FigJam tools are on in the figjam and all profiles. They cover stickies, shapes with text, connectors, tables and code blocks. Setup defaults to design.
How is this different from Flaude or Figma’s own MCP?
Deskhand runs on your machine with no relay, reads back every write, and publishes its tool count and tools-list size. It is £5 a month.
Is it open source?
Deskhand is a fork of magic-spells/figma-mcp-bridge, released under the MIT licence, with the original copyright kept. The licence key gates the server, not the code.
What about refunds?
The 14-day trial is there so you can find out before you pay. If you subscribe and it is not right, email hello@deskhand.studio within 14 days of the first charge and you get that charge back in full, no questions. Renewals are not refunded: cancel from the customer portal before the next one and access runs to the end of the period you paid for.
Which Claude plans does it work with?
Any Claude plan that supports MCP servers in Claude Code or Claude Desktop.
Claude,inyourfile.
One command, four steps, 14 days free. Your components, your canvas, checked before you trust it.