Anima MCP connects your AI agent to Figma. It still needs a system
By The WAALEE Team · · 4 min read
Anima shipped its own MCP server this year, a hosted endpoint that connects Claude Code, Cursor, or any MCP-compatible agent straight to Anima Playground and a linked Figma file. The pitch is the same one this whole category keeps making: stop pasting screenshots into a prompt, let the agent read the real file. It's a genuine improvement over screenshot-and-hope. It also runs on the same assumption every Figma-to-code tool has run on for two years, that the design system you're building from already exists, in Figma, in a shape worth reading.
What Anima MCP actually hands an agent
Per Anima's own writeup, the server exposes file structure, component relationships, and design-system assets to a connected agent, so it can implement a screen the way someone who actually understands the project would, matching existing patterns instead of guessing them. For a team that's handed off an Anima project or a specific Figma feature to an agent, that's a real step up from a static export. The agent sees the component tree, not a flattened PNG.
The part that only works if Figma already has the answer
Every capability in that pitch is downstream of one condition: a Figma file with a real, current design system already sitting in it, components, variables, a library someone maintains. That's true of Anima MCP the same way it was true of Figma's own Dev Mode MCP server when it shipped last year. Neither tool can navigate to a URL and pull a system out of thin air. Both need a node-id, a file, and permission to open it. If your brand's real design decisions live in a shipped website instead of a maintained Figma library, which is most companies past their first six months, there's nothing here to connect to.
- A founder who's never opened Figma but has a live site that already looks right.
- An agency picking up a client whose old design file is gone, outdated, or was never made, the site was built straight in code.
- A team benchmarking a competitor's site, where no one is ever handing over the Figma file.
- Anyone rebuilding a reference site they admire rather than one they have edit access to.
Read the rendered page instead of the source file
None of those situations are dead ends, they just need to start from a different source of truth. A live site is the same design system rendered, fonts resolved, colors computed, spacing laid out, just without the Figma layer names attached. Point a tool at the URL instead of the file, pull the real computed palette, type scale, spacing, and radii, and you get back the same kind of structured input an agent needs, W3C-format tokens instead of a component tree, ready to hand to Claude, Cursor, or whatever built the Anima project in the first place.
Three ways a coding agent gets design context right now, and what each one requires you to already have:
- Anima MCP: Hands an agent file structure, components, and design-system assets from a connected Anima Playground project and Figma file. Requires an existing Anima project and access to the Figma file behind it.
- Figma Dev Mode MCP: Same underlying constraint from Figma itself: variables and component data, but only for files you can already open, and only past a certain seat tier.
- WAALEE: Paste any live URL, no Figma file or Anima project required, and get real colors, type scale, spacing, and W3C tokens back as AI-ready prompts for Claude, Lovable, v0, Cursor, and Bolt.
Use each one for the system it can actually see
None of this is a knock on what Anima built. A hosted MCP endpoint that gives an agent real component relationships instead of a screenshot is a solid piece of infrastructure, and it'll save real time for teams whose system already lives where it expects to look. The gap is the one this category keeps leaving in the same place: a pipe to Figma is only as useful as what's already in Figma. If your brand's actual source of truth is a live URL instead, the fix isn't a better MCP server, it's reading the page the system was built for in the first place.