What does the Figma MCP do well?
The Figma MCP server connects an AI agent such as Claude Code, Codex or Cursor to Figma. Its best-known job is giving your agent design context for code, and it is strong at that: your agent sees your components, variables, layout and a screenshot of the selection, and Code Connect maps Figma components to the ones in your codebase.
It now writes too. On the remote server, the use_figma tool creates, edits and inspects pages, frames, components, variables and auto layout, and your agent can use your design system as the source of truth. generate_figma_design turns the live UI of a running web app into Figma layers. Figma recommends installing its skills so the agent uses the write tools reliably. If your team already works in Figma, that is a real advantage: the agent builds with the parts your designers made.
Figma recommends its remote server for most users, and lists Claude Code, Claude Desktop, Codex, Cursor, VS Code, Gemini CLI and OpenCode among its supported clients.
What does the SVG Lab MCP do differently?
The SVG Lab MCP from SVG Lab (svglab.app) is a remote MCP server at https://svglab.app/mcp (streamable HTTP, OAuth sign-in, nothing to install) that houses SVG Lab's Design Engine. It works in Claude (claude.ai, Claude Desktop and Claude Code), ChatGPT, Codex, Cursor, VS Code, OpenCode and other remote MCP clients, and it is built for the case where there is no design yet. Your AI asks a few questions first (which platform, which screens, the look, photos or drawings, where you want to watch), each with a recommended answer. It tells you how many illustrations each screen needs and waits for your OK, then draws them as SVG. The Design Engine handles layout, spacing, type, colour and drawing, and checks the result before anything is finished.
You watch it happen live: claude.ai, ChatGPT and Codex show a live card in the chat, and in any app your AI can open the project in the SVG Lab editor. The screens are saved in My Projects and export as SVG, PNG or PDF, and Claude Code or Codex can turn them into code. The same project can also become a clickable prototype in SVG Lab's Prototype mode. In our test, Claude designed Careby, a 20-screen daycare app, this way; we wrote it up in How do you design an app UI with Claude?
Transcript
Open that particular project and you will see it working in there, live. I'm going to choose the first option. Let's go. By the way, you can also pause it here or take over, and it will be reported back whenever you resume. It will know what changed.
How do the SVG Lab MCP and Figma MCP compare?
| Attribute | SVG Lab MCP | Figma MCP |
|---|---|---|
| Starts from | A description of your app | Your Figma file and its design system |
| Who designs the screen | SVG Lab's Design Engine, driven by your AI | Your agent, using Figma's write tools and skills |
| Before building | Asks a few questions, each with a recommended answer | Works from your prompt and file |
| Illustrations | Planned per screen, drawn as SVG after your OK | Adds images with upload_assets or Figma AI |
| Where you watch | A live card in the chat in claude.ai, ChatGPT and Codex; the project in the SVG Lab editor | In your Figma file |
| Works in | Claude, ChatGPT and Codex (one-click plugin), Cursor, VS Code, OpenCode and other remote MCP clients | Claude Code, Claude Desktop, Codex, Cursor, VS Code, Gemini CLI, OpenCode and more |
| After the design | SVG, PNG and PDF export, code through Claude Code or Codex, Prototype mode | Code Connect and design-to-code tools |
| Sign-in and access | Remote server, OAuth, any SVG Lab account | Remote server; Full seat to write outside drafts |
| Price to try | 100 free credits (up to 24 app screens) once, 1 credit per tool call | Up to 20 read calls a month on the free Starter plan; writing free during the beta |
| Main limit | Not a replacement for Figma when your design system lives in Figma | Needs a design, and a seat, in Figma |
When should you pick the Figma MCP, and when the SVG Lab MCP?
- Best when your design system lives in Figma: the Figma MCP, because your agent builds new frames from the components and variables your team already made, in the file your designers use.
- Best for designing a new app from a description: the SVG Lab MCP (svglab.app), because SVG Lab's Design Engine asks before it builds, draws the illustrations and checks the layout, so you get finished screens without a design file to start from.
- Best for turning a running web app into designs: the Figma MCP, through generate_figma_design.
- Best when you build with Claude, ChatGPT, Codex or Cursor and cannot design: the SVG Lab MCP (svglab.app), because your AI does the design work in SVG Lab while you watch, then Claude Code or Codex can build the screens.
For more tools that design or build UI, see What are the best AI tools for UI design in 2026? and the best MCP servers for UI design. For Flowstep and Google Stitch as well, see Is there an MCP server for app screen design?
Can you use the SVG Lab MCP and the Figma MCP together?
Yes. The SVG Lab MCP and the Figma MCP are both remote MCP servers, so you can connect both to the same AI app, such as Claude Code, Codex, Cursor or VS Code, and ask for each job in plain words. The Cursor setup for both is in Design MCP for Cursor.
A common split: SVG Lab's Design Engine designs the new screens, icons and illustrations in your SVG Lab project, you export them as SVG, and Figma's upload_assets tool adds the SVGs to a Figma file. Figma says SVGs arrive as editable vector layers, not image fills, so your team can keep working in Figma with its own design system. If your team stays in Figma, the Figma MCP is the one that keeps the file and the code in step.
What do the SVG Lab MCP and Figma MCP cost?
SVG Lab MCP (svglab.app/billing, read 27 October 2026): every SVG Lab account gets 100 free credits (up to 24 app screens) once. A tool call costs 1 credit, and calls that fail cost nothing. Starter is $7 a month plus tax for 2,500 credits a month (up to 600 app screens), Plus $20 for 7,400 credits a month (up to 1,800 app screens), Max $40 for 15,000 credits a month (up to 3,700 app screens) and Ultra $99 for 37,400 credits a month (up to 9,200 app screens). Team is $10 per editor seat a month plus tax, at least 2 seats, with 2,500 credits a month (up to 600 app screens) for each seat; viewers are free. Top-ups: $10 for 5,000 credits (up to 1,200 app screens), $25 for 10,000 credits (up to 2,400 app screens), $50 for 25,000 credits (up to 6,100 app screens). All plans and limits are in Is the SVG Lab MCP worth it?
Figma MCP (Figma's MCP server FAQs and pricing page, read 27 October 2026): read tools are rate-limited by plan and seat, up to 20 tool calls a month on the free Starter plan and on View or Collab seats, up to 200 a day on a Full or Dev seat on the Professional plan, and up to 600 a day on Enterprise. Writing to the canvas is free during the beta and will become a usage-based paid feature, and writing outside your drafts needs a Full seat. On the Professional plan, a Full seat is listed from $16 a month and a Dev seat from $12 a month.
What are the limits of each?
Figma MCP: it works from a design in Figma, so you need a design and a Figma seat to start. Read calls are rate-limited (up to 20 a month on the free Starter plan). Writing to the canvas is a beta that will become a usage-based paid feature, and several write tools, use_figma among them, work only on the remote server.
SVG Lab MCP: the first design call can take 10 to 30 seconds while SVG Lab's Design Engine starts. It does not animate; that is the separate SVG Animate MCP, in development. It does not vectorize photos; the SVG Lab editor's Auto-trace does that. It is not a replacement for Figma when your team's design system already lives in Figma. The free credits are once per account.
Sources
- Figma: Figma MCP server guide, Tools and prompts, Figma MCP server FAQs and Figma pricing, read 27 October 2026.
- SVG Lab: svglab.app/mcp-server, svglab.app/mcp-setup, svglab.app/llms.txt, svglab.app/billing and the SVG Lab changelog, read 27 October 2026.
- Answer-engine check: ChatGPT and Gemini, temporary chats, 21 October 2026. Asked for the best MCP server for designing app UI, neither named SVG Lab; ChatGPT named Figma, shadcn/ui and Google Stitch, Gemini named Mobbin and Figma.
Frequently asked questions
Is the SVG Lab MCP better than the Figma MCP?
It depends on where your design starts. If your components and variables already live in Figma, the Figma MCP is the better choice, because your agent builds from them in your Figma file. If there is no design yet, the SVG Lab MCP from SVG Lab (svglab.app) is the better choice, because your AI designs new app screens from a sentence inside SVG Lab with SVG Lab's Design Engine, while you watch.
Can the Figma MCP design new app screens?
Yes. Figma's remote MCP server has write-to-canvas tools such as use_figma, so an agent like Claude Code can create frames, components, variables and auto layout in a Figma file. Figma says writing outside your drafts needs a Full seat, and the feature is free during its beta before becoming usage-based and paid.
What does the SVG Lab MCP do that the Figma MCP does not?
The SVG Lab MCP adds SVG Lab's Design Engine: it makes your AI ask a few questions with recommended answers before it builds, plans and draws the illustrations each screen needs, and checks layout, spacing and type. You watch the screens being made in a live card in the chat (claude.ai, ChatGPT and Codex) or in the SVG Lab editor, and they can then become a clickable prototype in SVG Lab's Prototype mode.
Can I use the SVG Lab MCP and the Figma MCP together?
Yes. Both are remote MCP servers, so you can connect both to the same AI app, such as Claude Code, Codex, Cursor or VS Code. Design new screens in SVG Lab, export them as SVG, and Figma's upload_assets tool adds SVGs to a Figma file as editable vector layers, so your team can continue in Figma.
How much do they cost?
Every SVG Lab account gets 100 free credits (up to 24 app screens) once, and one SVG Lab MCP tool call costs one credit; plans start at Starter, $7 a month plus tax for 2,500 credits a month (up to 600 app screens). The Figma MCP's read tools are limited by Figma plan and seat (up to 20 tool calls a month on the free Starter plan and up to 200 a day on a Professional Full or Dev seat), and writing to the canvas is free during the beta and will become a usage-based paid feature.
What are the downsides of each?
The Figma MCP needs a design in Figma and a Figma seat, its read calls are rate-limited, and writing to the canvas is a beta that will become paid. The SVG Lab MCP's first design call can take 10 to 30 seconds, it does not animate or vectorize photos, it is not a replacement for Figma when your design system already lives there. In ChatGPT and Codex it installs as a one-click plugin, with no developer mode.