Skip to content
Black Friday 50% off + 15,000 credits Ends Nov 30 Ends Nov 30 see the deal
Black Friday15,000 free credits + 50% offends Nov 30

Drive your WordPress sites from Claude Code, Cursor or Codex

WPOS speaks MCP, so Claude Code, Cursor, Codex or an agent you wrote yourself can drive the same tools WPOS's built-in agent uses, against the WordPress sites you already run. Your model, your bill: no WPOS credits spent.

DRIVING WORDPRESS FROM YOUR AGENT
THROUGH WPOS
WIRING IT YOURSELF
How your agent connects
MCP, out of the box
A REST client you maintain
Which agents work
Claude Code, Cursor, Codex, any MCP client
Whichever one you built for
Building a page
A tool call
Hand-rolled block JSON
Page builders covered
Gutenberg, Elementor, Divi
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
WPOS credits used
None: you pay your model provider
Not applicable
Your host and database
Unchanged
Unchanged
How it fits

Your agent, WPOS's tools

WPOS speaks MCP, the open protocol AI agents use to call tools. Claude Code, Cursor, Codex or an agent you wrote yourself can drive the same tools WPOS's built-in agent uses, against the WordPress sites you already run.

Connect it from the AI Agents tab in Settings: the outside assistant signs in with your WordPress account and gets the same tools the agent uses, so every action runs as you and checks your WordPress permissions.

Driving a site from your own agent doesn't spend WPOS credits; you pay your model provider. Site licensing is unchanged, and the WPOS plugin stays on each site, because it is what exposes the tools.

What your agent gets

The same tools as the built-in agent

Native builds in any builder

Pages and sections in Gutenberg, Elementor or Divi, plus widgets, themes and components.

Media, users, SEO and WooCommerce

The same site tools the built-in agent uses, against the sites you run.

Reads the site safely

Read-only queries, file reads and a log tail, instead of direct database access.

Undo a bad change

Per-page backups and widget revisions, whichever agent made the change.

Plugins' own abilities

WPOS drives the WordPress abilities your plugins register, Elementor's and Angie's among them.

Both agents, one site

The built-in agent in wp-admin for designers and account managers, your own agent for developers.

How it works

Connect once, work from your editor

  1. 01

    Connect the site to WPOS

    Install the WPOS plugin and connect the site to your account.

  2. 02

    Open the AI Agents tab

    In Settings, connect your MCP client. It signs in with your WordPress account.

  3. 03

    Give it a job

    Ask for a page, a fix or an audit; it uses the same tools as WPOS's agent.

  4. 04

    Review and ship

    Check the result in the preview and publish when it is right.

Elementor Ultra, open source

For teams that build Elementor sites as code, Elementor Ultra is an MIT-licensed open-source stack from the WPOS team: write typed JSX components, compile them to native Elementor V4 pages, and deploy them over REST. The result is a normal Elementor page, editable in the editor, with no lock-in. It is separate from the WPOS product and not affiliated with Elementor Ltd.

Setting up a client for the first time? Claude for WordPress compares five ways to connect Claude to a site, and Claude Code for WordPress walks through a working developer setup.

Bring your own agent, answered.

What connects over MCP, what it can reach, and what it costs.

Book a Call with Founders

Yes. WPOS speaks MCP, so Claude Code, Cursor, Codex or any MCP client can drive the same tools as WPOS's built-in agent against the sites you already run.

No. Driving a site from your own agent doesn't spend WPOS credits; you pay your own model provider. Credits pay for work done by WPOS's own agent, and site licensing is unchanged.

Build and edit pages natively in Gutenberg, Elementor or Divi, write widgets, themes and components, manage media and users, handle SEO and WooCommerce, and read the site through read-only queries, file reads and a log tail.

Yes. The plugin is what exposes the tools on each site. What changes is which agent sits on the other end of it.

It signs in with a WordPress account and every action checks that account's capabilities, so it can do only what that user can. Bad changes can be undone with per-page backups and widget revisions.

Yes, and most do: the built-in agent in wp-admin for account managers and designers, your own agent for developers.

Black Fridayends Nov 30

Start free with 15,000 credits.

Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.

Claim 15,000 credits