What to ask a connected agent

Browse first

A request that begins "build me a site" lets the agent take the first design that seems to match. A request that begins "look through the library and tell me what fits" makes it read the whole library in brief and think about your product before committing. On uberdesigner's server, that look is one call and does not count toward a free account's templates, so there is no reason to skip it.

Compare options

Ask for two or three, never one and never ten. For each, ask for the name, a link to its page, whether your plan opens it, and one line on how your product would sit in it. Open the links yourself. The agent has read descriptions; you are the one who can look.

If the best fit is beyond your plan, a good answer says so in one line and still leads with what you can open.

Name the template

Once chosen, use the name. "Get the template emil ostrev" is unambiguous and makes the agent call the tool that fetches one template. "The second one" works in the same conversation and fails in the next.

From the uberdesigner MCP page, one request in this spirit: "Build my photography portfolio from the uberdesigner template emil ostrev, with the 30 photos in ./photos." It names the template, the subject and the files in a single sentence.

Say what is yours

1. Photos and images. The folder, the count, the order. Mention aspect ratios if they differ from the design's.
2. Copy. A file with one heading per section, or the lines pasted into the message. Say that lengths should stay close to the original.
3. Data. Prices, dates, menu items, projects, in a file with real values.
4. Identity. Your name, your accent colour in hex if you want it swapped in, your links.
5. Limits. What must not be touched in an existing project: files, routes, tokens.

Keep the design

Say it in one flat sentence: keep the typefaces, sizes, spacing, colours, components and motion as designed. Agents like to improve things. A template's values were tuned against each other, and a helpful adjustment to one of them is how a build drifts from the preview.

Ask for content in its natural form as well. A timetable stays a grid. A balance stays a number. A product is shown as the product, not as an icon of one.

After the build

Two follow-ups are worth knowing. If you want to see how the page came together, uberdesigner's server can replay a finished build element by element, optionally as a video. If you want it online, the server has a deploy guide for Cloudflare hosting with Supabase for data and R2 for media. Ask for either in plain words.

The five habits in one request

Use the uberdesigner server for this.

Browse: I'm building [what, e.g. a booking site for a two-chair barbershop in Leeds]. Look through the library once.

Compare: give me three ways to go. For each: the name, the page link, free or Pro, and one line on where my content would sit in that design. Lead with what my account opens. Stop there.

(After I answer.)

Name: get the template [name].

Mine:
- Copy in ./content/copy.md, one heading per section.
- [number] photos in ./content/photos, in order, mostly [4:5].
- Opening hours and prices in ./content/facts.json.
- Accent [#hex]. Links: [booking URL], [Instagram], [phone].

Keep: the template's typefaces, sizes, spacing, colours, components and motion, unchanged. Hours stay a table, prices stay numbers. If something of mine doesn't fit a section, ask me; don't redesign the section.

Build with Vite + React + TypeScript and plain CSS, run it, and check 390px, 1440px and reduced motion.

Written for this page as a starting point; swap the parts in [brackets] for your own. The full prompt of each uberdesigner template is longer and specific to one finished design, and it is tested by rebuilding the template from the prompt alone.

Keep reading

• What is a design MCPA plain definition of a design MCP server, what it replaces in a design-to-code workflow, and the things it does not do.
• 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.
• Design MCP permissions and safetyGood practice for connecting any MCP server to an AI agent: trust, what tools ask for, browser sign-in over pasted keys, and reviewing what the agent writes.

• Whole websites
• UI components
• Design morphing