You browse
You find a pricing page with the perfect colors and button style, and save it to PocketUI.
PocketUI's MCP server gives ChatGPT, Claude, Cursor and other AI agents direct access to your saved colors, fonts, components and screenshots. Add one link, sign in, click Allow.
Early supporters get 30% off their first year. No spam, ever.
You find a pricing page with the perfect colors and button style, and save it to PocketUI.
You open Cursor or Claude Code and want those exact colors. The AI has no idea what you saved.
Back to the tab, grab a hex code, paste it in the prompt. Forty times per project.
PocketUI's MCP server kills that loop entirely.
Save colors, fonts, SVGs, screenshots and full components from any website, into folders like "Dark SaaS" or "Pricing".
Add PocketUI's URL to ChatGPT, Claude, Cursor or any agent, sign in and click Allow. No keys to copy.
Say "use the palette from my Dark SaaS folder" and the AI pulls the real values from your library. No guessing.
{
"mcpServers": {
"pocketui": {
"url": "https://pocketui.app/api/mcp"
}
}
}ChatGPT or Claude? Paste https://pocketui.app/api/mcp as a connector. Every agent
HEX, RGB, HSL, Tailwind tokens. Grouped by folder.
Font families, weights, sizes, line heights. Ready for CSS or Tailwind config.
Saved sections exported as HTML + Tailwind. AI can reference and adapt them.
Visual references AI can see and match against.
Clean SVG code, ready to drop into any project.
Full extractions from a single page: colors, fonts, spacing, all at once.
They solve different problems. Design in Figma first? Use Figma's. Build from what you find on the web? Use this. Use both if you do both.
| PocketUI MCP | Figma Dev Mode MCP | |
|---|---|---|
| Source | Any live website | Your Figma files only |
| Setup | Browse + save + connect | Design in Figma first |
| What it exposes | Colors, fonts, components, code, screenshots | Figma layers, styles, variables |
| Best for | Using real-world inspiration directly in code | Implementing your own Figma designs |
| Works without Figma | Yes | No |
The MCP server gives Cursor the exact colors, font sizes and component structure, so the pricing table it writes matches on the first try.
A solo founder saves the best bits of ten SaaS sites. When building, the AI pulls buttons from one, colors from another, type from a third.
Instead of interpreting a picture, the AI reads the actual colors, fonts and code that were saved.
PocketUI's MCP server works with any tool that supports the Model Context Protocol, including ChatGPT, Claude, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI and Codex. If your tool supports MCP servers, it works with PocketUI.
Only the design assets you've saved to PocketUI. color palettes, fonts, components (as HTML + Tailwind code), screenshots, SVGs, and bookmarks. Everything is organized by folder. The AI can only read your library, never modify it.
No. Add PocketUI's URL to your AI tool, sign in and click Allow. For scripts or tools set up by hand, a personal token from Profile → AI works too.
No. MCP access works on every plan, Free included, so you can connect your AI tool and try it on your first saves. Free is 50 saves in total; Pro and Studio make the library unlimited.
Figma's MCP exposes your Figma file layers and design tokens. PocketUI's MCP exposes design inspiration you've saved from live websites: real colors, fonts, and components from sites you admire. They solve different problems and work well together.
No. The MCP server is read-only. AI tools can query your folders, read saved assets, and use the values in code generation. but they cannot add, edit, or delete anything in your library.

Join now and get 30% off your first year as an early supporter.
A quick confirmation now, then one email on launch day.