Originally published on Crafttor.

TL;DR: With the Figma MCP connected, Claude can act inside your Figma file. Pair Figma MCP Claude access with WebCapture to Figma and you get a live, clickable copy of a website sitting next to its editable frame. The plugin captures the page and writes the prompt. Claude does the one step a plugin cannot: it adds the code layer. This guide walks through the setup, the exact order of steps, and the small fixes that trip people up.

What you are building

You will end up with two things side by side on your canvas.

  • An editable frame. Frames, text, images and vector icons, laid out the way the browser laid them out. This is what you design on.
  • A code layer. The same page as a ready-to-run HTML, CSS and JS project. Hover states respond, CSS animations play and links work. If you recorded a flow with the Chrome extension, it replays.

The plugin's own one-liner sums it up: "A frame looks like the page. A code layer runs it."

Why Claude has to do the last step

Figma plugins cannot create code layers. The Plugin API simply has no way to make one. So WebCapture splits the work in two.

  1. The plugin captures the page, builds the frame and prepares a runnable project.
  2. It then hands you a prompt. Claude, with the Figma MCP connected, uses that prompt to add the project as a code layer beside your frame.

Before you start: the Figma MCP Claude checklist

Tick these off first. Most failed attempts skip one of them.

You need Why
WebCapture to Figma installed It captures the page and writes the prompt
A Figma file where code layers are available on your plan Claude needs somewhere to place the layer
Claude with the Figma MCP connected This is how Claude reaches into your file
An Apify API token, or the Chrome extension URL capture runs on Apify; the extension handles logged-in pages

Connecting the Figma MCP to Claude

MCP (Model Context Protocol) is the standard way to give an AI assistant access to outside tools. Figma offers an MCP server, and Claude can connect to it as a connector. In the Claude app you add it from the connectors settings. In Claude Code you register it as an MCP server. Either way, you approve Figma access once with your own Figma account.

A quick test: ask Claude to describe the frames in a file you share by link. If it can read them, the connection works.

Step 1: Capture the page into Figma

Open WebCapture to Figma in your file and pick a source.

  • From a URL. The page renders in a remote browser on Apify. You add your own Apify API token once, and a free Apify account is enough to start.
  • From the Chrome extension. Use this for pages behind a login or a bot wall. You capture the page as you see it, then paste the result into the plugin. No token is needed on this path. The walkthrough in importing a logged-in page to Figma covers it in detail.

Choose a width: Desktop 1440, iPad 820, Pixel 7, iPhone 14 Pro, iPhone SE, or a 360px Android phone. Run the import.

Read the import summary when it finishes. It tells you how many links were wired as prototype connections. That number is a quick sanity check that the capture saw the navigation you expected.

Capture or rebuild only designs you own or have permission to use.

Step 2: Decide whether you want a recorded flow

A code layer already plays hover states, transitions and CSS keyframe animations. It also follows links. What it cannot invent is a sequence of clicks you never made.

If the point of the layer is to demo a journey, such as opening a menu and choosing a plan, record that flow with the Chrome extension first. The flow then replays in the code layer. The full method is in recording a website user flow.

If you only need the page to feel alive under the pointer, skip this step.

Step 3: Copy the prompt from the plugin

After the import, press Copy prompt in the plugin. The prompt gives Claude everything it needs to add the captured project as a code layer beside your frame.

You do not need to edit it. Resist the urge to "improve" it with extra instructions. Every line you add is something Claude might act on in a way you did not intend.

Keep Download HTML in mind as well. It saves the same page as a ready-to-run HTML, CSS and JS project, with its images and Google fonts inside. That is handy for keeping a local copy or opening the page in a browser.

Step 4: Paste the prompt into Claude

Open a new Claude conversation with the Figma MCP connector enabled. Paste the prompt and send it.

Then let it work. Claude reads the prompt, talks to your file through the MCP and places the code layer beside the imported frame. If Claude asks for permission to use a Figma tool, approve it. That approval is the MCP doing its job.

A few habits that make this smoother:

  • One page per conversation. A fresh chat keeps the context clean.
  • Do not chat in between. Wait for Claude to report that it finished before asking anything else.

Step 5: Set the size, then press play

Code layers cannot be resized from the API. So Claude cannot set the final dimensions for you. The prompt names the size the layer should be.

Select the new code layer, type that width and height into the design panel, then press play. Hover a button. Watch an animation loop. Click a link. If you recorded a flow, walk through it.

If the layer looks cropped or squashed, the size is the first thing to check.

Troubleshooting

Claude says it cannot reach Figma

The MCP connection is not active in this conversation. Check that the Figma connector is enabled, and that you approved access with the account that owns or edits the file.

The layer appeared but looks wrong

Check the size first. It must match the size the prompt named. Then check that you pressed play, since a code layer that is not running looks static.

An animation shows on the code layer but not on the frame

That is expected. WebCapture detects hover states, transitions, keyframe animations, scroll-reveal effects and sticky or fixed positioning. It saves them with each layer as plugin data. A Figma prototype cannot replay CSS animations, so on the frame they are recorded. In a code layer they play. For more on this split, read hover states and animations in Figma.

Some images are missing

If the page served images only to logged-in users, capture it through the Chrome extension instead of by URL.

What stays private

The URL you enter is sent to Apify so the page can be rendered. Nothing from your Figma file is uploaded. Captures pasted from the extension stay on your machine. The plugin never sends anything to an AI. You paste the prompt into Claude yourself, so you always see what goes in.

Where this fits in your workflow

Use the pair for jobs where behaviour matters as much as layout.

  • Redesign reviews. Put the live page next to your new frame and compare interactions, not just pixels.
  • Developer handoff. Let engineers hover and click the current component instead of reading a description of it.
  • Stakeholder demos. Walk a recorded flow inside the Figma file, with no browser tab switching.

Install WebCapture to Figma, capture one page, and try the Copy prompt step with Claude. The plugin is free.

FAQ

Can WebCapture create the code layer without Claude?

No. The Figma Plugin API has no way to make a code layer, so no plugin can create one. WebCapture prepares the project and the prompt. Claude, through the Figma MCP, adds the layer.

Do I need a paid Apify plan?

No. A free Apify account is enough to start with URL capture. You add your own API token once. The Chrome extension path needs no token at all.

Why can't Claude set the code layer size?

Code layers cannot be resized from the API. The prompt tells you the size, and you set it in the design panel before pressing play.

Is WebCapture to Figma free?

Yes. WebCapture to Figma is a free plugin. URL capture runs on your own Apify account.

Can I use ChatGPT instead of Claude for this step?

The Copy prompt flow is written for Claude with the Figma MCP connected. If you want an AI to rebuild the page as new code instead, use Copy for LLM from the Chrome extension, which works with a code layer's AI, Claude or ChatGPT.