MCP for website templates

Pick by how the site behaves

A template is easiest to judge by its idea: what is on the first screen and what the visitor does with it. A portfolio where photographs hang on a turning helix suits someone with thirty strong images. It does not suit a consultancy with four paragraphs. When the agent proposes options, ask it to say in one line how your material would sit in each. That line shows a mismatch faster than a screenshot does.

Hand over content as files

Put the copy in one text file and the images in one folder, in display order, and state the counts. Thirty photos in a design made for thirty is a clean swap. Eight photos in the same design is a decision, and you want the agent to raise it before building, not to stretch eight images across thirty slots.

The same goes for data: prices, dates, a menu, a list of projects. Real values in a file get placed. Values described in a sentence get approximated.

What your plan opens

Through uberdesigner's server, taking a template returns its prompt and, when your plan opens it, its project. With a free account the agent rebuilds a free template from the prompt. On a monthly or yearly plan it can start from the project, which is the same site as the preview, and change the content inside it. If a template is locked for your plan, the agent is told so and should pass the message on as it is.

When the site is ready to go live, the same server has a deploy guide the agent can follow: Cloudflare for hosting, Supabase for data and R2 for media.

What a whole-site request should contain

• The template's name, once you have chosen, or a request for three options if you have not.
• The subject in two lines: what it is and who it is for.
• Paths: the copy file, the image folder, the data file.
• Counts: how many images, products, projects or dates.
• The rule: keep type, spacing, colours, components and motion as designed.
• The check: run it, two widths, reduced motion, and a list of anything changed.

A prompt to start from

Use the uberdesigner server and get the template [template name, e.g. dj-zak]. Build my site from it in this folder.

My site: [name], [what it is in one line], for [who]. The one action is "[button label]", which goes to [URL or email].

Start from the template's project if my plan opens it; otherwise rebuild from its prompt. Stack: Vite + React + TypeScript, plain CSS. Add no libraries the template doesn't use.

Keep the design exactly: typefaces, sizes, spacing, colours, components, timings and easing. Replace only the subject:
- Copy: ./content/site.md, one heading per section in page order. Keep each line close to the original's length. If mine is much longer, tell me instead of shrinking the type.
- Images: ./content/images, [number] files named 01 to [number], in display order.
- Data: ./content/[dates / prices / projects].json.
- Accent: [#hex] in place of the template's accent. Leave every neutral.

If a section of the template has no counterpart in my content, list it and ask. Do not fill it with invented text and do not delete it silently.

Then run it. Check 390px and 1440px wide, check that every image loads, and check the reduced-motion version. Report what differs from the template.

Needs a coding agent (Claude Code, Codex CLI, Cursor or similar) with the uberdesigner MCP server connected and signed in. The named template must be one your plan opens.

Keep reading

• What to ask a connected agentFive habits for requests to an agent with a design MCP: browse first, compare options, name the template, say what is yours, and tell it to keep the design.
• How to choose a design MCPFive criteria for judging a design MCP server: what its tools return, who made the designs, how you sign in, what counts against your plan, and whether results are checked.

• Claude Code
• Cursor and editors
• Codex and terminal agents
• Chat apps
• UI components
• Design morphing