Out of the box, Cursor and Claude Code write UI from whatever you type and whatever is in your repo. MCP servers give them the rest: the actual design, a browser to look at the result, the right components and current docs. The difference shows most in frontend work, where "make it look like this" is the whole task.
These are the servers worth adding for UI and design work, grouped by the job they do. Commands and URLs are taken from each project's docs at the time of writing; check the linked README before you rely on a flag.
How to add any of them
Claude Code, remote server:
claude mcp add --transport http <name> <url>
Local package:
claude mcp add <name> -- npx <package>
Cursor, in ~/.cursor/mcp.json:
{
"mcpServers": {
"remote-example": { "url": "https://example.com/mcp" },
"local-example": { "command": "npx", "args": ["-y", "some-mcp-package"] }
}
}
Restart Cursor and check the MCP panel; in Claude Code run /mcp.
1. Design input
Figma MCP: your own design files
Figma's official server gives the agent the structure of a selected frame, its variables, styles and components, so it builds from the design instead of a screenshot. Remote URL: https://mcp.figma.com/mcp. Best when your team designs in Figma first. The Figma MCP setup guide covers seats, limits and the desktop variant.
MiroMiro MCP: live websites
When the reference is a site that already exists (a competitor, a site you're migrating, an inspiration page) there's no Figma file to read. MiroMiro's server reads the live URL in a real browser and returns:
- the section's real rendered code as Tailwind, HTML, React or Vue (
extract_code) - the site's brand: logo, colors, fonts (
extract_brand) - its full design tokens as CSS variables or a W3C tokens file (
extract_design_tokens) - its images, SVGs, fonts, videos, audio and Lottie files
claude mcp add --transport http miromiro https://miromiro.app/mcp
Free account, 300 credits a month, no card; the client opens a sign-in page the first time. In Cursor, use the one-click install or add {"url": "https://miromiro.app/mcp"} to mcp.json. Then ask things like "rebuild the pricing section of linear.app in our components" and the agent calls the right tool. Client-by-client setup.
Figma and MiroMiro pair well: Figma for screens you designed, MiroMiro for sites you're referencing.
2. Seeing the result
Playwright MCP: let the agent use a browser
Microsoft's Playwright MCP gives the agent a real browser it can navigate, click and read through accessibility snapshots. Useful for "open localhost:3000 and check the signup flow works" and for checking a page after a change. Local package: @playwright/mcp.
Chrome DevTools MCP: debug what the browser sees
Google's Chrome DevTools MCP connects the agent to DevTools: console messages, network requests and performance traces. Reach for it when the UI is wrong and you need to know why, such as a failed request or a layout shift. Local package: chrome-devtools-mcp.
3. Components
shadcn MCP: the right components, not invented ones
If your project uses shadcn/ui, the shadcn MCP lets the agent browse and install components from the registries you configure, so it uses the real component instead of writing a look-alike. The shadcn CLI sets it up for your client (npx shadcn@latest mcp init).
4. Docs
Context7: current library docs
Models are trained on older versions of fast-moving libraries. Context7 fetches current, version-specific docs and examples on request, so the agent writes Tailwind v4 or Next.js code that matches the version you actually use. Remote URL: https://mcp.context7.com/mcp.
5. Web content (not design)
Firecrawl MCP: pages as text for the model
Firecrawl's server scrapes and crawls pages into clean markdown, which is what you want when the agent needs a site's words: docs, articles, product data. It's the counterpart to MiroMiro: Firecrawl for content, MiroMiro for design. Local package: firecrawl-mcp (needs a Firecrawl API key).
A starter setup for UI work
| Job | Server | Why |
|---|---|---|
| Build from your designs | Figma MCP | Frames, variables and components from your files |
| Build from live sites | MiroMiro MCP | Real code, tokens, brand and assets from any URL |
| Check the result | Playwright MCP | The agent opens the page and clicks through it |
| Use your components | shadcn MCP | Real registry components, not look-alikes |
| Current docs | Context7 | Version-correct examples |
Install the two or three that match the work you repeat, and add more only when you hit the gap. A shorter tool list keeps the agent quick to pick the right one.
Next: connect MiroMiro to Claude, Cursor or ChatGPT in under a minute, or read what an AI agent needs to match a real website's design.
Skip the maintenance - one API call
Design tokens, brand data, fonts, SVGs, images, and section code from any URL. 300 free credits a month, no card.
Soraia · Founder, MiroMiro
Building MiroMiro: a browser extension and API that extract design tokens, assets, and production-ready code from any live website. The gotchas in these posts come from the extraction engine's own commit history.
Follow on X