Point your own agent at your WordPress.

WPOS speaks MCP, so Claude Code, Codex, Cursor or an agent you wrote yourself can drive the same tools the built-in agent uses — pages, widgets, themes, media, users, SEO, WooCommerce and read-only introspection — against the WordPress you already run.

Read the docs Book a Call with Founders
OUTCOME DRIVEN

Ship More Client Sites Without Hiring More People*

Outsourced
In-House
Agency Partners
WPOS

*Comparing 1 Operator + WPOS to 1× dedicated resource per category.

As an Agency using primarily WordPress, this AI is a game changer regarding managing, selling and working within WordPress.

WPOS is one of those, once you use you never go back application.

Anthony DeFelice
Anthony DeFelice Amplus Agency Founder & CEO
57 Sites, One Agency
42s Build, Check, Verify
50,000 Page Store, One Site
See It In Action Book a Call with Founders
BRING YOUR OWN AGENT

Already have an agent? Point it at your WordPress.

WPOS speaks MCP, so you can drive your WordPress sites from Claude Code, Codex, Cursor, or any MCP-eligible agent — your model, your workflow.

Claude Code

Run WPOS from the terminal you already live in.

Codex

Connect it once and give it the whole site surface.

Cursor

Edit widgets, pages and content without leaving your editor.

Any MCP client

No lock-in to one vendor's model or one vendor's chat window.

Or just use the agent built into WPOS. Either way it stays native WordPress — your hosting, your database, still yours to edit by hand.

Start free — no card
DRIVING WORDPRESS FROM YOUR AGENT
OVER THE WPOS MCP SERVER
WIRING IT YOURSELF
How your agent connects
MCP, out of the box
A REST client you maintain
Which agents work
Claude Code, Codex, Cursor, any MCP client
Whichever one you built for
Building a page
A tool call
Hand-rolled block JSON
Page builders covered
Elementor, Divi, Gutenberg
One, if you wrote for it
Reading the site safely
Read-only queries, file reads, log tail
Direct database access
Undoing a bad change
Per-page backups and widget revisions
Your own backups
Your host and database
Unchanged
Unchanged

Bring your own agent, answered.

What connects over MCP, what it can reach, and what we will not pretend about.

See the docs

Yes. WPOS exposes an MCP server, so Claude Code, Codex, Cursor or any MCP-capable client can drive the same tools the built-in agent uses, against the WordPress you already run.

Any that speak MCP. Claude Code, Codex and Cursor are the ones we see most often, and an agent you wrote yourself works the same way, because the protocol is the interface rather than a particular vendor.

The same things the built-in one does: build and edit pages, write widgets, themes and components, manage media and users, handle SEO metadata and schema, work with WooCommerce, and read the site through read-only queries and file reads.

Yes. The plugin is what exposes the tools on your site, so WPOS installs into the WordPress you already run either way. What changes is which agent sits on the other end of it.

In your WordPress database, on your hosting. There is no migration and no hosted duplicate of your site. WPOS does need its backend service to run, so it is not an offline or air-gapped tool — but the site itself never moves.

Yes, and most teams use both. The built-in agent lives in wp-admin next to the site; MCP is there for when you would rather work from your own editor or drive the site from somewhere else.

Use the agent you already work in.

The docs cover connecting an MCP client to your site — or take 15 minutes with the founders if you would rather be walked through it.

Read the docs