Describe it. Review it. Ship it.

Proper structure, lean markup, your own design tokens. Assembled by an agent, and yours to pull apart afterwards.

Speaks MCP, so it works withClaude CodeClaude DesktopCodex CLICodex DesktopCursorOpenCodeAny MCP Client
harbourline-sailing.org
YouPut the next few courses on the front page, newest first
Oxyum
wiring up the query
The front page reads your course dates directly now, so the list reorders itself as new ones go up.
  • Found your course fields
  • Built the loop
  • Sorted by start date

It starts by saying it out loud

A shop, a directory, a members area, a portfolio. Whatever the job is, the first move is the same — you describe it, in your own words.

Why it holds up

An agent is only as good as what it is allowed to touch

Point a general-purpose tool at a website and you tend to get one impressive page that quietly rots: styles pinned to elements, pages that know nothing about each other, markup nobody wants to open twice. Oxyum gives the agent the same primitives a careful developer would reach for — post types, templates, components, tokens — so what comes out survives contact with the second and third page.

thornbury-roastery.com
YouSell our coffee subscriptions as products people can browse and buy, each with its own page
Oxyum
setting up your content types
Subscriptions are real WordPress content now, with one template driving every product page, so a new blend arrives already styled.
  • Registered a subscription post type
  • Built a template bound to your fields
  • New products style themselves

Under the hood

The unglamorous parts, done properly

Most tools hand you a generic layout and leave you to reconcile it with the site you already have. Oxyum reads the site first.

Post types and templates

Content modelled as post types, fields and templates, bound to your data rather than pasted into a page.

Your design system

Components, classes and tokens. Change one definition and every page that uses it moves.

Reads the whole site

The agent looks at what you have already built and matches it, instead of inventing a style island.

Live content

Query loops and field bindings, so the page keeps up with the database on its own.

Lean by default

Native Oxyum markup. Fast pages, no wrapper soup, nothing to untangle later.

Editable to the selector

Every element stays yours to adjust by hand. Keep prompting, or take over entirely.

The canvas

Take the wheel whenever you like

Everything the agent produces opens in the Oxyum editor. Nudge a breakpoint, rewrite a selector, restructure a section by hand — or carry on prompting. It gets you most of the way in seconds. The canvas is where the last ten per cent happens.

Look at the editor

atelier-brun.fr
YouBuild the shop mega menu with every collection and category in it
Oxyum
assembling your menu
Mega menu is in, pulling your collections and categories live, styled from your existing tokens.
  • Built the shop mega menu
  • Pulled categories from your taxonomy
  • Opened it in the canvas for you

Setting up

Three steps to your first build

1

Connect your agent

Point any MCP client at your WordPress install. Oxyum exposes the builder to it.

2

Say what you want

A page, a post type, a whole site. It reads what exists before it writes anything new.

3

Finish it yourself

Open the result in the canvas and take it the rest of the way by hand.

oxyum — zsh
$ npm create oxyum

Hand the boring half to your agent

Connect it once, describe what you need, and spend your time on the parts that actually need you.