# Paper MCP alternatives for website design research [Open the live Fudge conversation](https://design.withfudge.com/share/paper-design-mcp-alternative-for-website-design-research) Last updated: 2026-08-25 For website design research, Paper MCP is strongest when you want an AI coding tool to work with an open design file. Fudge is stronger when you want to search and inspect captured websites as references. Choose Paper for designing and editing inside a shared canvas. Choose Fudge for finding patterns across websites and turning observed details into implementation guidance. ## Choose by the job Use Paper when your starting point is a design file. Paper's local MCP can read and write the currently open file, so it fits a workflow where a designer and an AI coding tool move design context between the canvas and code. Paper also supports tokens for color, typography, spacing, containers, breakpoints, and radius. See the [Paper MCP documentation](https://paper.design/docs/mcp) and [Paper design tokens documentation](https://paper.design/docs/tokens) for the supported workflow. Use Fudge when your starting point is a website, screenshot, or saved design reference. It can search a captured public library or saved references by description and observed design details. It can then inspect page structure, sections, components, layout, viewport, and page state. That makes it useful before implementation, when you are still deciding which patterns fit the page you need to build. The practical distinction is the source material. Paper connects an agent to an editable design workspace. Fudge helps an agent investigate website examples and compare what is visibly present. These are different jobs, so the best choice depends on what you already have. The examples below are useful references for this kind of research. Raycast places trust and product proof close to its main action. boringBar uses a clear rhythm of screenshots and short explanations. Monocle keeps a restrained utility presentation while varying its feature composition. Cosmos shows how readable text can sit on a warm editorial canvas. Compare hierarchy, proof placement, text width, and visual density before borrowing any pattern. ## Captured pages [![Raycast - Your shortcut to everything](https://pin.fontofweb.com/4674?format=jpg)](https://design.withfudge.com/share/pin-4674) [Raycast - Your shortcut to everything](https://design.withfudge.com/share/pin-4674) [![boringBar - Taskbar Dock Replacement for macOS](https://pin.fontofweb.com/8813?format=jpg)](https://design.withfudge.com/share/pin-8813) [boringBar - Taskbar Dock Replacement for macOS](https://design.withfudge.com/share/pin-8813) [![Monocle for macOS - Noise-cancelling for your screen](https://pin.fontofweb.com/5622?format=jpg)](https://design.withfudge.com/share/pin-5622) [Monocle for macOS - Noise-cancelling for your screen](https://design.withfudge.com/share/pin-5622) [![Welcome to Cosmos](https://pin.fontofweb.com/4489?format=jpg)](https://design.withfudge.com/share/pin-4489) [Welcome to Cosmos](https://design.withfudge.com/share/pin-4489) ## What Fudge adds to reference research A website review can cover more than the headline layout. You can inspect font families, font files and variants, sizes, weights, and line heights. You can also inspect color roles, frequency and contrast, spacing, borders, radii, shadows, gradients, component styles, images, crops, motion, overlays, and clipping when those details are present in the capture. A repeatable research pass looks like this: 1. Save several references with a similar visitor goal. 2. Search for a pattern such as a compact hero, proof near the main action, or a warm editorial layout. 3. Inspect each candidate at the same viewport or page state. 4. Record shared choices and meaningful differences. 5. Compare those observations with your own page before writing code. You can ask an AI coding agent to use the observations as constraints instead of asking it to copy a page blindly. Fudge lets you also identify fonts, find similar fonts, review a website, compare references, and inspect color contrast. Supported observations can be exported to Tailwind v4, CSS, JSON, or DESIGN.md. ## A quick decision checklist Pick Paper first if: - You already have an editable design file. - The agent needs to change frames, components, or tokens in that file. - Your team wants the design canvas to remain the source of truth. Pick Fudge first if: - You need to research public websites or saved captures. - You want to compare several references before choosing a direction. - You need observed fonts, colors, spacing, page structure, or component details. - You want implementation notes in Tailwind v4, CSS, JSON, or DESIGN.md. Many teams can use both. Research website patterns in Fudge, then carry the resulting decisions into Paper or code. Keep the boundary clear: a reference inspection describes what was observed. It does not create ownership of another company's internal design system. ## Use this in your AI agent > Compare Paper MCP and Fudge for my website design research workflow. First decide whether my source material is an editable Paper file or captured website references. If it is website research, organize the review around page structure, typography, colors, spacing, proof placement, responsive behavior, and component patterns. Use the references below as inspiration, separate shared observations from choices that should remain original, and recommend a concrete next step for my page. > > [Use Fudge with your AI agent](/mcp) --- Yes. Use Fudge during reference research and Paper during design development. First collect a small set of website references that match the visitor goal. Compare their page structure, typography, color roles, spacing, proof placement, and responsive choices. Keep a short decision record that says which patterns are useful, which are unsuitable, and what you will make distinct. Next, move those decisions into your own layout and token choices in the open Paper file. Paper's MCP is then useful for keeping the design workspace connected to the AI coding process. Fudge remains useful when you need to check another website, revisit a saved capture, identify a font, compare references, or inspect contrast. This division keeps an editable design file and a website reference library focused on their separate jobs. --- Ask for an evidence-first review of five areas: the first screen's hierarchy, the path from headline to main action, typography families and weights, color and contrast roles, and repeated component patterns. Add responsive checks for container width, text wrapping, navigation behavior, card stacking, and image crops. Require the agent to separate observation from recommendation. Ask it to list what is visibly present, compare at least three references, identify recurring patterns, and propose an original combination for your page. If you have captures, include the visitor goal and target viewport. That gives the agent enough context to choose relevant examples rather than copying the most visually distinctive page. ## Related questions - [Paper Design vs Fudge for design references](/share/paper-design-vs-fudge-for-design-references) - [Paper MCP vs Fudge for AI coding agents](/share/paper-design-mcp) - [Refero alternative with design system export](/share/refero-alternative-with-design-system-export) - [Refero.design MCP guide: Refero vs Fudge](/share/refero-design-mcp-guide-eea94f)