Docs

Your assistant can already write code. What it does not have is the trade of selling — which section comes first, what a buy box has to contain, why a three-pack tile needs a photograph of three units and not one photo scaled up.

uxgen gives it that trade, and the parts to build with. Ask for a product page and your assistant stops inventing what a selling page looks like: it places parts that were drawn, filmed and measured for the job, and it refuses the ones that would make your store look generated.

It runs on our side. Nothing is downloaded, nothing runs on your machine, and nothing has to be kept up to date.

• 206 parts on the shelf
  173 for e-commerce · 33 for SaaS. Buy boxes, price ladders, bundle builders, cart drawers, free-shipping bars, proof walls, pricing tables. 173 of them are built for a store that takes money; 33 for a product that sells a subscription.
• Photographs of your own product
  Not stock, not a category picture. You bring the product; the server photographs it for the page it is about to sit in.
• An audit that opens a real browser
  Five widths, the computed styles, and a robot that clicks the buying path. It names each gap with its selector and the gesture that closes it — never a score.
• The source, in your project
  Your assistant writes the files where you already work. uxgen never writes to your disk and never touches your store.

There is nothing to install and no API key to paste. You point your client at one address; the first call opens your browser, you sign in, and your client keeps the token from then on.

• Cursor
  add the JSON block below to ~/.cursor/mcp.json (or .cursor/mcp.json for one project)
• ChatGPT
  developer mode on, then Plugins > + > paste https://www.uxgen.ai/mcp as the connection URL
• Lovable
  Connectors > + > MCP server > Server URL https://www.uxgen.ai/mcp, authorise with OAuth

For any client configured by file, this is the block:

{
  "mcpServers": {
    "uxgen": { "type": "http", "url": "https://www.uxgen.ai/mcp" }
  }
}

Thirteen of the fourteen tools answer today. The last one (`ameliorer`) returns an explicit refusal that names why.

uxgen hands your assistant HTML blocks and one locked grammar — a single palette, one type scale, one radius, one motion curve for the whole store. Your assistant ports them to Liquid for Shopify, to JSX for Next.js, or leaves them as plain HTML.

It asks for no Shopify key, no Stripe key and no analytics access. It does not host your store, does not connect to it, and never reads your orders or your customers.

If you already have a store, uxgen never rewrites your page. Two modes, and improve is the default when your sentence says a store exists (“I already have”, “keep”, “don’t rebuild”, “my store is at …”). Asking for a new store wins over the possessive: “build my store” is a rebuild, “improve my store” is not.

• Improve — the default
  Your theme is inherited, not recomputed: your assistant passes your current page as heriteDe and your fonts, radii and grounds become the grammar. The audit runs in conservation with conserver: true and returns only what can be added or fixed without rebuilding — a missing bundle scale, a guarantee, a sticky buy bar, a dead link — each addition with its anchor: “after the buy box”, “before the footer”. Each part is inserted with uxgen_piece at that anchor. Nothing else moves. Before anything is published you get a per-section diff (kept / changed / added) of your page.
• Rebuild — only when you ask for it in those words
  “Rebuild it”, “from scratch”, or a brand-new store: the construction path — skeleton, recipe, imagery, the page laid by the engine. Say it, and it happens. Do not say it, and nothing on your page moves.

These are refused at the source, not flagged afterwards. The code in brackets is what comes back so your assistant knows which one it hit.

• A star rating with no order behind it
  note-sans-avis
• A review with no source
  avis-sans-source
• A countdown that re-arms on reload
  compte-a-rebours
• A discount off a price nobody paid
  pourcent-orphelin
• A figure with no method and no date
  chiffre-invente
• A generated image presented as an untouched photograph
  photo-non-retouchee
• A total that only shows up at checkout
  cout-total-absent
• An option the buyer picked and was never charged for
  option-valeur-non-facturee

• Product Pages — $19/month
  70 generated photos a month · Fair use: 30 components a day
• Whole Store — $49/month
  180 generated photos a month · No daily limit
• Agency — $199/month
  730 generated photos a month · No daily limit

Every plan gets the same fourteen tools, the same 206 parts and the full source in your repo. Only the volume changes. There is no free trial. You stop with one email to hello@uxgen.ai, and you keep every page your assistant shipped — the files are in your project, not in ours.

• URL
  https://www.uxgen.ai/mcp
• Transport
  streamable-http — remote, over HTTP
• Authorisation
  OAuth with PKCE (S256) on first use. There is no static API key.
• Registry name
  ai.uxgen/ecommerce-conversion

It never touches your disk. No tool takes a file path and no tool writes a file. You send content, you get content back, and you write it: read your file, pass it as html, save what comes back.

This is the list tools/list serves. Each line gives the tool, what it returns, and a sentence you can say out loud to your assistant to reach it.

• uxgen_brief
  Loads the design law and the plan of the page before a single line of HTML is written.“Read the uxgen brief for a coffee brand selling one roast in tins.”
• uxgen_theme
  One locked grammar for the whole store: palette, type scale, radius, one motion curve. Returns CSS to paste as-is.“Give me the uxgen theme for this brand and paste the CSS.”
• uxgen_image
  Makes the imagery the page needs (scene or packshot), framed and captioned, for the merchant's own product.“Make the hero image for the tin, three units, one light.”
• uxgen_packshot
  Puts the brand's own label on a product shot, checks the subject really is that product, and refuses the result when it comes out dirty.“Packshot my jar with this label, cut out.”
• uxgen_render
  Renders the page and hands the images back in the answer at 390 and 1440, so the agent can look at what it just built. Nothing is written to any disk.“Render the page and show me the captures.”
• uxgen_audit
  Measures the rendered page and names each gap with its selector and the gesture that closes it. Never a score.“Audit this page and list what costs a sale.”
• uxgen_ameliorerrefuses today
  Reworks one section at a time, and has the first screen judged by an outside eye that does not know which version is new.“Improve the first screen of this page.”
• uxgen_publier
  Refuses to publish a file that carries someone else's brand, or a claim with no source behind it.“Publish the page.”
• uxgen_status
  Current job, licence, image credits, repository.“What is the uxgen status?”
• uxgen_seo
  Turns one seed keyword into an SEO plan on live Google data: monthly traffic, difficulty, who holds the top of the page today, and what to write to take it. The search-data key stays on the uxgen server.“Give me the uxgen SEO plan for 'ai website builder' in the US.”
• uxgen_demarrer
  Opens a store and returns a recipe template already assembled: the sections in the measured order, one text field per line, and the image budget priced before a single photograph is bought.“Start a uxgen store for a coffee brand selling one roast in tins.”
• uxgen_poser
  Takes the filled recipe and PAINTS the page: no HTML, no CSS, no tag written by you. Returns the assembled page with its photographs, and one product sheet per product.“Lay out my uxgen store from the recipe I just filled in.”
• uxgen_catalogue
  Searches the library of parts by words, by brief, or by an image, and returns the ones that fit the moment of the page you are building.“Search the uxgen catalogue for a buy box with a subscription toggle.”
• uxgen_piece
  Returns one part of the library as the two files an agent needs: the self-contained HTML and the prompt that built it. A free account opens a preview set; a paid plan opens all 168.“Give me the CAPTCHA-01 part uxgen_catalogue just showed me.”

Thirteen of the fourteen tools answer today. The last one (`ameliorer`) returns an explicit refusal that names why. Its judge is a vision model and no vision key is posed on this server. The refusal says so. Do not invent its result.

Two separate gates, and they fail differently. Measured against https://www.uxgen.ai/mcp on 31 August 2026:

• Open to anyone, no token
  tools/list answers 200 with all 14 tools and their full input schemas. Registries and agents can read the surface before anyone signs in.
• Needs an account
  tools/call, resources/list and resources/read answer 401 without a token, and the body carries the sign-in URL so your client knows where to send you.
• Needs an active subscription
  With a token but no live plan, every tools/call returns a refusal that names itself and carries reessayable: false — that is a decision, not an outage, so an agent must stop rather than loop. Only an active subscription opens; a lapsed or trial state does not.
• Draws on a monthly allowance
  uxgen_image spends your photograph allowance, which differs by plan. uxgen_seo spends a separate one and is available from Pack up, because the live search data is bought through our key.

On the website itself, the home page shows 67 of the parts to anyone, with no account. /library and /pieces both redirect a visitor who is not signed in — measured, same day, same way as the endpoint above.

Three static files, generated from one source so they cannot drift apart from each other or from this page:

• /mcp.md
  The long form: install, every tool, the refusals, the price.
• /llms.txt
  The short index, for a model that only wants the shape.
• /.well-known/mcp/server.json
  Registry metadata: name, transport, remote URL.

Everything above that carries a number was read from the running system, not typed. Three things on this page were not, and saying so is cheaper than being caught:

• The four install procedures
  The endpoint is proven to answer — tools/list was called against production and returned 14 tools. The four client procedures themselves are written from each client’s own documentation and were not run end to end from this page: the OAuth round trip needs a browser and an account. If one of them is wrong for your client, write to hello@uxgen.ai and it gets corrected here.
• The daily component figure
  “5 components a day” is a published fair-use policy, not a meter. Nothing on the server counts components per day today. We would rather write that than let you discover it.
• Conversion
  No number on this site claims a lift, and no tool honestly can. What uxgen ships is the mechanics a page needs before a lift is even possible, and an audit that names the ones you are missing.

Write to hello@uxgen.ai. A question that had to be asked is a page that was missing.