Mobbin MCP alternatives: UI reference servers for Claude Code, Cursor and Codex

By Screenrove editorial · 2 October 2026

Mobbin’s MCP server needs a paid plan. Here is what a design MCP does, how Mobbin’s, Refero’s and Screenrove’s compare, and how to connect a free one in a minute.

Ask a coding agent to build a pricing page and it will produce something that looks like every other generated pricing page. The model is working from a blurred average of the web. A design MCP server changes that by letting the agent look up real screens from shipped products before it writes any code.

Mobbin’s MCP server made the idea popular. It needs a Pro or Team plan, though, so people search for alternatives. Here is how the main options compare.

What a design MCP server does

MCP (Model Context Protocol) lets an agent call tools on a remote server. A design reference server typically lets the agent:

• search a library of real screens by pattern, such as onboarding, pricing or settings;
• fetch a screenshot and its notes so the model can see the layout;
• pull design details such as colors, type sizes and spacing;
• hand you a choice instead of picking on its own.

The agent then builds from a concrete reference instead of from memory.

How the options compare

Prices and features were checked on each product’s own pricing page on 2 October 2026. They change, so confirm before you buy.

Mobbin MCP

Mobbin lists Claude Code, Claude, Cursor, Codex, ChatGPT and several other clients, and gives agents access to its whole library. If you already pay for Mobbin, use it: nothing else has that breadth, especially for mobile.

Refero MCP

Refero’s server exposes its styles, screens and flows. It comes with Pro, Team and Lifetime plans, not the free tier. It is the natural choice if you already prefer Refero’s search.

Screenrove MCP

Screenrove’s server is free and needs no account. The library is much smaller and covers desktop web products only, such as Linear, Stripe, Vercel, Notion, Airbnb and Figma. In exchange, each product is documented in depth, and the tools are built around the way agents work:

• search_screens finds screens by pattern across all products.
• pick_reference opens a page in your browser with a few options side by side. You click one and the agent collects your choice. In Claude and ChatGPT the picker can appear in the chat.
• get_design returns a product’s measured design guide as DESIGN.md, with colors, type scale, layout and component notes.
• get_flow and list_flows return a signup or onboarding sequence with what happens between screens.
• check_my_ui and compare_screens compare a description of your screen with real ones, such as plan counts on a pricing page or the length of an onboarding flow.
• build_handoff packages the references into a build prompt.

Connect it in a minute

The server address is https://screenrove.com/mcp. In Claude Code:

claude mcp add --transport http --scope user screenrove https://screenrove.com/mcp

In Codex:

codex mcp add screenrove --url https://screenrove.com/mcp

In Cursor, add {"mcpServers":{"screenrove":{"url":"https://screenrove.com/mcp"}}} to ~/.cursor/mcp.json. The agents page has one-click buttons for Claude, Cursor and VS Code, plus setup for ChatGPT and Windsurf.

Prompts to try

• “Find me some pricing page references on Screenrove and let me pick one.”
• “Show me three onboarding flows and let me choose one for our signup.”
• “Get Linear’s design guide and use its product palette for our settings screen.”
• “Check my onboarding against real products on Screenrove.”

Which one should you use?

If you pay for Mobbin or Refero, use the server that comes with your plan. If you don’t, or you build web products and want measured design details rather than only screenshots, start with Screenrove’s free server. You can run more than one; agents handle several MCP servers at once.

Comparing the libraries themselves rather than their servers? See the best Mobbin alternatives.