An interface animation almost always gets lost between the mockup and the code. The designer tunes an easing curve to the hundredth of a second, the developer copies it “by eye,” and what ships to production only half resembles what was approved. Figma Motion, Figma’s animation timeline, in open beta since June 24, 2026, tackles this problem from one end. The Figma MCP server, which passes those animations to a coding agent like Claude Code, tackles it from the other.
This article walks through the full workflow as of October 8, 2026: what the agent actually receives, how to install it, a step-by-step first animation, what doesn’t carry over yet, and what it costs. Sources: Figma’s announcement and release notes, the MCP server developer documentation, its pricing page and the official skills Figma publishes on GitHub. Fourth article in our series, after the Claude Code and motion design guide, the Remotion tutorial and the HyperFrames vs Remotion comparison.
The 30-second answer
On the Figma side: the designer animates
- a timeline in the same file as the mockups;
- position, scale, rotation and opacity keyframes, ready-to-use animation styles;
- video export (MP4, WebM), GIF, SVG and, since September 30, Lottie;
- copyable code in CSS, JSON or React with motion.dev from Dev Mode.
On the Claude Code side: the agent implements
- you paste it the link to an animated frame, it reads the structure, then the motion;
- the
get_motion_contexttool gives it the keyframes, the curves and precomputed code; - it merges the two into your project’s components;
- the MCP server is free during its beta, but capped according to your Figma seat.
Figma Motion in October 2026: what actually exists
Motion is a mode of Figma Design, just like Draw or Dev Mode. You switch a frame to Motion mode and a timeline appears below the mockup. You drag layers to adjust their timing, scrub the playhead to preview any moment, and set keyframes for position, scale, rotation and opacity, independently of one another. Comments can target a specific moment in the animation, which changes how you get a motion reviewed.
Three building blocks make it more than a presentation gimmick. Animated components: the animation travels with the component across every file, like its color or typography. Motion variables: an easing curve defined once, with modes, that updates every animation referencing it. And theFigma agent, which places real keyframes on the timeline from a written prompt.
The September 30, 2026 update added custom animation styles (saved, combined, published to a library), audio on the timeline with MP4 and WebM export, text animation by character, word or line, andLottie and dotLottie export. The release note specifies that these styles can be applied by coding agents via MCP. 3D transforms, announced in June with a waitlist, don’t appear in the release notes as of this article’s date. And the whole thing remains in open beta.
The workflow: from the timeline to the component
The key point is in step 2. The MCP server doesn’t deliver the animation in one block: get_design_context describes the structure (hierarchy, sizes, styles, assets, linked components), by default in React with Tailwind, and get_motion_context describes the motion. According to the documentation, this second tool returns the inventory of animated layers, the keyframe tracks with their curves, precomputed CSS @keyframes and motion.dev code snippets, and coordination hints for layers that move together. With the option recursive: true, it covers all descendants of a frame in a single call, up to 500 layers according to Figma’s skill.
The official skill figma-implement-motion, shipped with the Figma plugin for Claude Code, says it plainly: the two responses are linked by the layer ID, “and that’s the whole workflow.” The agent starts from the list of animated layers, finds each one in the structure, and grafts the motion onto it. It also requires reusing the timing and curve values as is, without recalculating them, because a custom curve or a spring effect loses fidelity with every reinterpretation. That’s exactly the problem the workflow is meant to solve.
Installing the Figma MCP server in Claude Code
Figma recommends its remote server, hosted at https://mcp.figma.com/mcp, which doesn’t require the desktop app and offers the most features. A local server also exists, via the desktop app, but it’s reserved for Dev or Full seats on paid plans and mainly targets enterprise needs.
| Step | Command or action | Good to know |
|---|---|---|
| Recommended route | claude plugin install figma@claude-plugins-official |
Installs the MCP server and the Figma skills, including the motion ones |
| Manual route | claude mcp add --transport http figma https://mcp.figma.com/mcp |
Server only, without the skills; limited to the current project by default |
| For all your projects | Add --scope user to the manual command |
Saves reinstalling the server in every repository |
| Sign-in | Restart Claude Code, type /mcp, choose figma, then Authenticate |
OAuth sign-in with your Figma account; the agent only sees the files you have access to |
Prefer the plugin: the difference comes down to the skills. They’re instructions the agent loads to know which tools to call, in what order, and which pitfalls to avoid. Without them, Claude Code has the same tools but has to guess the method. If you’re new to the tool, our getting-started guide to Claude Code covers the basic installation.
Step by step: a first interface animation
Take a common case: a dashboard’s “what’s new” card, which slides and fades in on open, with its badge growing slightly just after.
1. Prepare the frame in Figma. Name layers explicitly, use your library’s components and variables, and animate in a reasonably sized frame. Figma’s documentation advises against selecting frames that are too heavy: the server’s response grows accordingly and the agent gets lost.
2. Animate. Switch the frame to Motion mode, apply a “fade” and “move” style to the card, then a scale keyframe on the badge, offset by a few tenths of a second. If your team has defined an easing curve variable, use it rather than a hand-entered curve.
3. Copy the link. Right-click the frame, then “Copy link to selection.” The remote server works by link: the agent doesn’t open the page, it extracts the file ID and the layer ID from it.
4. Give Claude Code the instruction. In your application’s repository, paste the link with a precise instruction:
Example prompt
“Implement the animation from this Figma frame in src/components/NewsCard.tsx: [link]. Fetch the structure first, then the motion context. Reuse our existing components and the animation library already in the project. Respect prefers-reduced-motion. Don’t change any other animation.”
5. Let the agent merge. It calls get_design_context, then get_motion_context on the same layer. On a React project without an animation library, it uses the motion.dev snippet; on a non-React site, the CSS snippet. If the project already uses another library, the skill tells it to adapt to that library rather than add a new one.
6. Check in the browser. This is the skill’s most useful rule: “renders without errors” doesn’t mean “renders correctly.” Reload the page, watch a full loop, check that each element moves at the intended moment, then turn on reduced motion in your operating system to check the resting state. Validate one animation before chaining twenty.
7. Review and ship. Have the designer review the result, ideally side by side with the frame’s video export, then commit. If several elements share the same animation with only an offset, check that the agent factored it out instead of copying it: the skill requires it, but it’s the kind of detail you verify.
What carries over, and what doesn’t yet
Figma’s skill keeps a list of features with no clean translation into code, with a caveat: it reflects a point in time, and if the tool returns a snippet for a feature deemed unsupported, the tool takes precedence. As of October 8, 2026:
| Animated element | Carried over to code via MCP | Fallback |
|---|---|---|
| Position, scale, rotation, opacity | Yes, with CSS and motion.dev snippets | None needed |
| Progressive stroke drawing (common cases) | Yes, simple cases; mixed settings carry over poorly | Keep the SVG and simplify the effect |
| Transitions between variants (Smart Animate) | No: a different data path, not yet integrated | States handled in code with a short transition |
| Mask that is itself animated | No | Animate the content, keep the mask fixed, or go through video |
| Arcs, shader effects | Motion exported, shader visual rendering not | Video export from Figma |
| GIF or animated SVG | Not via MCP | Manual export from Figma, or Lottie |
The row that matters most for a product team is the third. Many “animated” interfaces in Figma rely on transitions between component variants. Those don’t go through get_motion_context for now: the skill asks the agent to recode them as states and flag it. If your prototype depends on them, factor it into the estimate.
The other way around: Claude Code animating in Figma
The MCP server can also write. The general-purpose tool use_figma creates and edits frames, components and variables, and a second skill, figma-use-motion, extends it to keyframes, animation styles, curves and timeline duration. In practice, Claude Code can animate an existing mockup from a prompt, which the agent built into Figma can also do.
Three caveats, all written in the skill itself. Access isn’t open to all accounts: if motion features are refused, the agent must stop instead of retrying. A screenshot only shows the resting state, never the motion: to check, the agent has to request a video render on the Figma side, which is slow and costly, from a few seconds to several minutes. Finally, writing to the canvas is, like the rest of the server, free during the beta but slated to become usage-based and paid.
For a small business, this reverse direction is mainly useful to prepare variants for a designer to decide on, not to replace their eye. It’s the same logic as for Claude Design: AI proposes fast, the human chooses.
What it costs: two meters to watch
According to Figma’s pricing page, Figma Motion is available with Full seats. The June announcement was more nuanced: access with limited exports on the free plan, full primitives and exports for Full seats on all plans, animated components, motion variables and the agent reserved for paid plans. On the code side, the MCP server has its own call quotas, which depend on the plan and the seat.
| Figma plan | Full seat (designer) | Dev seat (developer) | MCP calls, Dev or Full seats |
|---|---|---|---|
| Starter (free) | — | — | 20 per month |
| Professional | $16/month (annual), $20 (monthly) | $12/month (annual), $15 (monthly) | 200 per day, 10 per minute |
| Organization | $55/month (annual) | $25/month (annual) | 200 per day, 15 per minute |
| Enterprise | $90/month (annual) | $35/month (annual) | 600 per day, 20 per minute |
Per-seat US prices from figma.com/pricing, as of November 2026 (checked November 2, 2026); call quotas from the developer documentation, checked October 8, 2026. View and Collab seats are limited to 20 MCP calls per month on all plans.
First meter: MCP calls. The recommended flow uses at least two read calls per animation (structure, then motion), often a third for a screenshot. With 20 calls a month, the free plan is enough to test on a few frames, not to work. A developer on a Dev seat in the Professional plan gets 200 calls a day, which comfortably covers a small team’s usage. The documentation warns that this service, free during the beta, will become usage-based and paid, with no date or pricing published.
Second meter: AI credits. Each seat includes a monthly volume of credits (3,000 for a Full seat on Professional, 500 for a Dev seat). Since October 6, 2026, when the Figma agent came out of beta, it has been consuming these credits. Having Figma’s agent animate a mockup and having Claude Code implement it are therefore two separate costs, on top of your Claude subscription. Before rolling it out widely, define the input and output data of these tools in your usage policy: that’s the topic of our article on Claude in business and data security.
Figma Motion, Remotion or HyperFrames?
Figma Motion + MCP
To animate an interface: micro-interactions, entrances, loading states. The deliverable is code in your application, designed by a designer.
Remotion
To produce videos in React, parameterized and at volume. Paid license from 4 people up.
HyperFrames
To produce videos in HTML, with ready-to-use recipes. Open source, Apache 2.0.
The three only compete on the surface. Figma Motion can export an MP4, but its real value is turning an interface into code. Remotion and HyperFrames, detailed in our comparison, are for making videos. A product team can perfectly well use Figma Motion for its application and HyperFrames for the launch video that presents it.
Frequently asked questions
How do you connect Figma Motion to Claude Code?
Install the Figma plugin with the command claude plugin install figma@claude-plugins-official, authenticate with /mcp, then paste the link to an animated frame into Claude Code. The agent reads the structure with get_design_context, then the animation with get_motion_context, and implements it in your components.
What does the get_motion_context tool return?
The list of animated layers, their keyframe tracks with easing curves, precomputed CSS @keyframes and motion.dev code snippets, and the groups of layers that share the same timeline, with their duration and loop mode.
Is the Figma MCP server free?
It’s free during its beta, but capped: 20 calls a month on the free plan or with a View or Collab seat, 200 a day with a Dev or Full seat on Professional or Organization, 600 a day on Enterprise. Figma says it will become usage-based and paid, with no date or pricing published as of October 8, 2026.
Do Smart Animate transitions carry over to code?
Not yet via the MCP server. Transitions between component variants follow a different data path, which Figma’s official skill declares not integrated. The agent must recode them as states with a short transition and flag it.
Can Claude Code create an animation directly in Figma?
Yes, with the use_figma tool and the figma-use-motion skill, which set keyframes, animation styles and curves. But these features aren’t open to all accounts, and a screenshot only shows the resting state: checking the motion requires a video render on the Figma side, which is slower.
In short
Figma Motion gives designers a timeline in the mockup file itself; the Figma MCP server gives Claude Code the structure and the motion, linked by the layer ID, with precomputed code. The workflow delivers on simple animations, which make up most of an interface, and still stumbles on transitions between variants, animated masks and shader effects. It’s in beta on both sides, free but capped on the MCP side, and Figma’s agent now consumes credits. Test it on one component, with a designer and a developer in the loop, before making it a team method. Last episode of the series: AI motion design in a small business, its costs and when to keep a motion designer. To frame these uses, explore our AI strategy engagements or contact us.