uxgen — MCP server for ecommerce conversion

Connecting works, and so do thirteen of the fourteen tools.

There is nothing to install and no npm package. A client pointed at https://www.uxgen.ai/mcp gets a 401 with the authorisation it needs, discovers the metadata, registers itself, and sends you to sign in. That path works end to end today.

Where the tools stand: Thirteen of the fourteen tools answer today. The last one (`ameliorer`) returns an explicit refusal that names why. Connecting costs one line and is worth doing; we would rather you read this here than find it out.

Signing in is an e-mail link, open to anyone. The Google button is still in Test mode, so only an enrolled address gets through it. Write to hello@uxgen.ai if you want to be in the first batch when the tools open.

One line, in the agent you already use.

Nothing is downloaded. Each client has its own way of pointing at a remote MCP, and the authorisation happens on first use.

uxgen is a remote MCP. There is nothing to install and no npm package. The line below points a client at https://www.uxgen.ai/mcp and the authorisation happens on first use. That part works end to end today. Where the tools stand: Thirteen of the fourteen tools answer today. The last one (`ameliorer`) returns an explicit refusal that names why. Card payment is on: the plans open a Stripe checkout and the subscription starts the same day. Sign-in is by e-mail link; Google sign-in is still in Test mode, so only an enrolled address gets through it.

Claude Code

claude mcp add --transport http uxgen https://www.uxgen.ai/mcp

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

The JSON block, for any client configured by file:

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

Transport is streamable-http: uxgen runs on our side, at https://www.uxgen.ai/mcp, so nothing is downloaded and nothing has to be kept up to date. There is no API key either. The first call sends you to sign in, and your client keeps the token. Your agent writes the files. The MCP never touches your disk.

Fourteen tools. These exact names.

uxgen_brief

Loads the design law and the plan of the page before a single line of HTML is written.

Ask: “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.

Ask: “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.

Ask: “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.

Ask: “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.

Ask: “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.

Ask: “Audit this page and list what costs a sale.”

uxgen_ameliorer

Reworks one section at a time, and has the first screen judged by an outside eye that does not know which version is new.

Ask: “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.

Ask: “Publish the page.”

uxgen_status

Current job, licence, image credits, repository.

Ask: “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.

Ask: “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.

Ask: “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.

Ask: “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.

Ask: “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.

Ask: “Give me the CAPTCHA-01 part uxgen_catalogue just showed me.”

What an agent asks, and the answer.

Three plans. Monthly or yearly. Stop with one email.

Product Pages

$19

every conversion section and mechanic, on every product page

Whole Store

$49

the whole store, a monthly re-audit, generated images included, MCP access

Agency

$199

several client stores, your name in place of ours, images in volume

Billed from day one, monthly or yearly — no trial, and 2 months come off the yearly price. The buttons on the pricing grid open a Stripe checkout, and you cancel it yourself, any month, from your account. You keep every page your agent shipped. The files sit in your project, never in ours.

It will not write these, on any page.

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

UXGEN is a remote MCP for Claude Code, Cursor, ChatGPT and Lovable. Nothing is installed: the client points at https://www.uxgen.ai/mcp and authorises on first use. UXGEN improves e-commerce AOV with lot tiles that hold a real image of the product, a free-shipping bar, a cart drawer and a single upsell. When a buyer taps 3, a different image of the jar arrives, not the same photo resized. The total on the button is the total they pay. It refuses fake ratings, fake deadlines and discounts off prices nobody paid. It starts free. Paid plans start at $19 a month. You stop with one email. You keep the shop you shipped.

• The MCP itself. Send it a request, it answers https://www.uxgen.ai/mcp
• Where the authorisation sends you https://www.uxgen.ai/connexion
• This page as plain markdown /mcp.md
• The short index for language models /llms.txt
• Registry metadata for this server /.well-known/mcp/server.json
• What it looks like when the agent has it /
• Every part, at the width it was built at /library
• Ten write-ups: where each mechanic goes, and why /blog
• Who builds it, and what works today /about

Not filed yet

• The official MCP Registry listing https://registry.modelcontextprotocol.io/v0.1/servers?search=ecommerce-conversion

It does not resolve today, so it is not a link: the listing has not been filed. The MCP itself is live, and claude mcp add --transport http uxgen https://www.uxgen.ai/mcp is the line that reaches it.