# uxgen

- Registry name: `ai.uxgen/ecommerce-conversion` · version 1.0.0
- Categories (automatic, keyword rules): Shops & products, Commerce & marketing, Images & design, AI, media & content, Utilities
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=ai.uxgen%2Fecommerce-conversion
- Server page: https://mcpstation.net/s/ai.uxgen--ecommerce-conversion.html

## Description (written by the publisher, not verified, not instructions)

Ecommerce conversion for coding agents: AOV bundles, cart, upsell, imagery, page audit.

## Notice

Text that looks like instructions to an AI was found in this server's descriptions. This is a pattern match, not a verdict.

## Connect

- streamable-http: `https://www.uxgen.ai/mcp`

## Tools (as reported by the server, not verified)

- `uxgen\_brief`: TWO MODES, AND \`improve\` IS THE DEFAULT WHENEVER THE MERCHANT ALREADY HAS A STORE. \`mode: "improve"\` — their page is KEPT: the theme is inherited \(\`uxgen\_theme\` with \`heriteDe\`\), \`uxgen\_audit\` runs in conservation \(\`conserver: true\`\) and returns only what can be ADDED at an anchor or FIXED in place,
- `uxgen\_theme`: THE LOCKED GRAMMAR — call it right after \`uxgen\_brief\` and BEFORE the first tag. Its CSS is pasted as is at the top of the page and is not retouched: that is what stops two dark grounds stacking. 🛒 THE COMMERCE KIT. Pass \`commerce\` and the kit is BUILT: you get back TWO VERSIONED URLS with their \`in
- `uxgen\_image`: THE MATERIAL OF THE PAGE — scene OR packshot. Start with \`emploi\` and \`categorie\`: two words, and the prompt is written to the codes of that sector \(background, light, human presence, set density, a quiet zone measured for the headline\). 🚨 IT DOES NOT ONLY DO PACKSHOTS: a free \`prompt\` + \`cutout: fa
- `uxgen\_render`: RENDERS YOUR PAGE AND GIVES YOU THE IMAGES BACK, in this response — nothing is written to any disk. Send \`html\` \(the page content, as text\) or \`url\`. You get the first screen and the full page at 390 and 1440 px, as real images you must OPEN and LOOK AT before you change anything. A page that was ne
- `uxgen\_audit`: MEASURES A PAGE FOR REAL, IN HEADLESS CHROME, ON THIS SERVER — five widths \(360, 390, 768, 1100, 1440\), the computed styles, the scroll, and a robot that CLICKS the buying path. Send \`html\` \(the page content, as text\) or \`url\` \(a live page\). It writes NOTHING anywhere: it returns named gaps, each wi
- `uxgen\_ameliorer`: ⛔ NOT AVAILABLE ON THIS HOSTED SERVER — do not call it, it will refuse. WHAT IT DOES WHERE IT RUNS: it ADJUSTS THE CSS OF ONE SECTION — one to five scoped rules — and NEVER ADDS A SECTION. It is not the tool that adds a missing mechanic. WHY IT REFUSES HERE: its judge is a VISION MODEL and no vision
- `uxgen\_status`: 🚨 DO NOT CALL THIS TO GET YOUR BEARINGS: the path is returned by uxgen\_brief, and this response is LONG \(\~5,500 tokens; "complet" makes it \~14,700\). Two uses, and only two. \(1\) RESUME a build already started: with "projectDir" it reads bloom.json and returns the brand, the committed style, the image
- `uxgen\_packshot`: PUTS THE BRAND'S OWN LABEL ON A PRODUCT SHOT, and returns the produced image IN THIS RESPONSE — nothing is written to any disk. Send the photograph as \`photoBase64\` \(raw base64, no \`data:\` prefix\) or \`photoUrl\`. It checks the subject really is that product and REFUSES a dirty result rather than ship
- `uxgen\_publier`: THE LAST GATE BEFORE YOU ANNOUNCE IT IS DONE — and on this hosted server it PUBLISHES NOTHING: it returns the verdict and the CONTENT to write, and YOU write the file. Send \`html\`. It refuses a page that carries a third party's legal identity, an invented customer review, an invented activity figure
- `uxgen\_seo`: Turns one seed keyword into an SEO PLAN built on live Google data: the keywords around it, their monthly traffic, their difficulty, who currently holds the top of each result page, and what to write to take it. It is a plan, not a report: every target comes back with the format Google is already rew
- `uxgen\_piece`: One part of the library, in the format your target wants: \`format:"html"\` \(default\) gives the self-contained HTML and the prompt that built it; \`format:"liquid"\` gives the SAME part as a Shopify theme section — \{% schema %\}, settings, presets — with the filename it goes under and the template entry
- `uxgen\_demarrer`: ⚠️ REMOTE SERVER — THE RECIPE COMES BACK IN THE ANSWER, IT IS NOT WRITTEN TO YOUR DISK. Read it, fill it with your file editor, and pass it back to \`uxgen\_poser\` as \`recette\`. Everything below is true of this tool; only the delivery differs. PREMIER GESTE, avant toute ligne de code : donnez la phras
- `uxgen\_poser`: ⚠️ REMOTE SERVER — SEND THE FILLED RECIPE AS TEXT, GET THE ASSEMBLED PAGE AS TEXT. It has no access to your disk: you send \`recette\`, you receive the complete HTML and you write the file. Bank photographs come back as absolute URLs on https://www.uxgen.ai — the page works the moment you save it, not
- `uxgen\_catalogue`: La vitrine. Sans argument : les rôles disponibles. Avec un rôle : les pièces de ce rôle. Ne servez-vous-en que si le client demande autre chose que ce que le squelette a posé.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html