The Aura Design Engine
One control room,
a whole engine underneath
Aura is the governed control room agencies run their fleets from. Underneath it is a family of open, composable engines — MCP servers, WordPress plugins, and agent skills — that let AI agents design, build, host, audit, and govern WordPress at fleet scale. Every one is wired for approvals, audit, and reversibility.
Design → Build → Host → Audit → Govern
The family spans the whole lifecycle of a WordPress site — and Aura governs every stage.
1Design
Compose and edit real Elementor pages, precisely.
2Build
Ship and maintain the site itself, on WordPress.
3Host
Drive servers, DNS, CDN, and backups underneath.
4Audit & Content
Read, score, and write content, SEO, and structured data.
5Govern
Approve, audit, snapshot, and roll back — the control plane.
The engines
Each one is a real, working engine that powers a part of Aura — not a separate product to juggle.
Design · Agent-native Elementor building
Aura Design Engine
A maintained, Elementor-4.x-correct engine that lets an AI agent build and edit real Elementor pages — sections, widgets, global classes — with reversible, snapshot-backed writes. It is the design layer beneath Aura's page workflows.
A maintained fork of msrbuilds/elementor-mcp (GPL-3.0), kept correct for modern Elementor.
Design · The agent recipe layer
SiteAgent Elementor Studio
A skill that teaches an agent how to drive the Design Engine well — the patterns, guardrails, and recipes for building on-brand pages instead of raw tool calls. Published on ClawHub; it's how the design work stays repeatable.
Build · The on-site WordPress agent
SiteAgent + Power Pack
The free WordPress plugin that gives Aura health, inventory, update, and maintenance reach into every site — plus a governed Power Pack of higher-privilege tools. This is how Aura acts inside WordPress without ever holding raw admin credentials.
Host · Infrastructure control
cloudways-mcp · hostinger-mcp
MCP servers that let an agent operate the hosting layer — servers, restarts, backups, cache, DNS — across Cloudways and Hostinger. They are the infrastructure engines Aura's provider operations run on.
Audit & Content · Content, SEO & structured data
wordpress-api-pro
A WordPress REST integration for reading and writing posts, pages, media, SEO meta, ACF, and JetEngine fields — the engine behind Aura's content audits and agent-authored content, with drafts-first, approval-gated writes.
Govern · The control plane over MCP
aura-mcp
The capstone: an agent-facing control plane that drives the agency itself — list pending approvals and snapshots, approve or reject actions, and roll runs back — all behind Aura's governance. It ties the family together into one governed loop.
Why one family, not a pile of tools
Point-tools edit one site. The Aura Design Engine is built so the same agent can carry a job across every stage — and Aura keeps the whole thing governed and reversible.
Governed at every stage
Mutating actions from any engine are risk-classified and approval-gated by default, and every call is recorded — who or what asked, who approved, what ran.
Reversible by design
Page-content snapshots before design writes, health-gated fleet updates with auto-rollback, and run-level rollback across the whole job. Agents move fast; Aura keeps it undoable.
Open and composable
MCP servers, a WordPress plugin, and agent skills — standard, inspectable pieces. Bring your own agent (Claude Code, Cursor, anything that speaks MCP); Aura is the governed gateway.