v3.15.4·112 MCP tools·free reads, licensed writes

Let your AI agent run WordPress.
Correctly.

One plugin and one MCP server give any AI agent a safe, complete control surface for Elementor, WooCommerce, Astra, Rank Math and Gutenberg. Every write is backed up, dry-runnable and re-rendered, so the page visitors see never goes stale.

Works with Claude Code, Cursor, Windsurf, Cline and any MCP client. Install in 30 seconds · All 112 tools

Works with any MCP-compatible AI tool

  • Claude Code
  • Claude Desktop
  • Cursor
  • Windsurf
  • VS Code Copilot
  • JetBrains
  • Zed
  • Cline
  • Roo Code
  • Continue
  • Aider
  • Amazon Q
  • Sourcegraph Cody
  • Gemini CLI
  • OpenAI Agents SDK
  • LangChain
  • CrewAI
  • AutoGen
  • Claude Code
  • Claude Desktop
  • Cursor
  • Windsurf
  • VS Code Copilot
  • JetBrains
  • Zed
  • Cline
  • Roo Code
  • Continue
  • Aider
  • Amazon Q
  • Sourcegraph Cody
  • Gemini CLI
  • OpenAI Agents SDK
  • LangChain
  • CrewAI
  • AutoGen

The Elementor problem

Every other AI tool gets Elementor wrong

Elementor keeps a page in three places: the element JSON, the generated CSS and the rendered HTML. Writing the JSON through the standard REST API leaves the other two stale, so visitors keep seeing the old page while the editor shows the new one.

Generic REST write

  • _elementor_data updated
  • _elementor_css stale
  • post_content stale

Looks saved. Renders old.

AgenticWP

  • _elementor_data updated
  • _elementor_css regenerated
  • post_content re-rendered

Saves through Elementor's own Document::save(), under a per-post lock, with a backup first and the element-ID set verified after.

Ships with a skill

Three job loops, with gates the agent cannot skip

The MCP package includes an agent skill (Claude Code, Cursor, Cline rules) built the test-driven way: scenarios run without it, failures recorded, the procedure written against them, then re-run. It turns 112 tools into three procedures.

A

Change

Connect → scope → read cheaply → dry-run one element per change type → batch write → verify on the rendered page → log. Staging-to-live transfers, site-wide settings, SEO sweeps.

find_elements · diff_elementor_element · update_elementor_elements · purge_cache

B

Build

Catalog → design system → tree → dry-run → write as draft → snapshot → reuse as template or bundle. Atomic Elementor 4 and classic both, palette tokens instead of hex.

list_elements · get_widget_schema · build_page · export_element

C

Maintain

Health report → inventory (search, broken links, menus) → the user confirms counts → fix per kind → verify numbers before and after. Renames, redirects, Gutenberg blocks.

site_health_report · search_content · edit_post_blocks · create_redirect

Rules that do not bend: no write before the connection proved which site it is · destructive operations need an explicit yes · scope boundaries hold even with the client's blessing · "done" needs evidence from the rendered page.

Install

30 seconds to the first tool call

  1. Upload the pluginWP Admin → Plugins → Upload. No settings to configure; reads work immediately.
  2. Create an application passwordUsers → Profile → Application Passwords. That is the only credential the agent gets.
  3. Run the MCP installerinstall.sh / install.bat creates a venv and writes .mcp.json; or register the server by hand in any MCP client.
  4. Talk to your agent"Audit this site", "move the testimonials section to the pricing page", "rename AquaPure to ClearFlow everywhere". The skill handles the rest.

Full install guide →

$ claude mcp add agenticwp \
    ~/MCP/AgenticWP/.venv/bin/python ~/MCP/AgenticWP/server.py \
    -e WP_URL=https://your-site.com \
    -e WP_USER=admin \
    -e WP_APP_PASSWORD="xxxx xxxx xxxx xxxx"

› agent_context()
  site: your-site.com · Elementor 3.30 · licensed · 112 tools
› site_health_report()
  score 81 · grade B · 4 findings

In production

Real client sites, before and after

Hover a card to see the page the client had before. Each case study lists the prompts, the numbers and what the guardrails refused.

Also in daily use on a 20,000-SKU WooCommerce catalogue, where the batch and bulk tools came from.

Pricing · USD

Lifetime, or yearly. Your call.

Every tier unlocks all 112 tools and the skill. Licenses are verified by a self-hosted service with a 7-day offline grace; the plugin and the MCP server auto-update. 14-day refund, no questions.

Agency Lifetime

$399 once

10 sites

  • Lifetime updates
  • Priority email support
  • All 112 tools + skill
Buy Agency Lifetime

Solo

$79 per year

1 site

  • ≈ $6.58 / month
  • Email support
  • All 112 tools + skill
Buy Solo

Agency

$249 per year

10 sites

  • ≈ $20.75 / month
  • Priority support
  • All 112 tools + skill
Buy Agency

Agency Pro

$499 per year

Unlimited sites

  • ≈ $41.58 / month
  • Slack support + onboarding call
  • All 112 tools + skill
Buy Agency Pro

What if you stop maintaining this?

The plugin and server are files you download and keep. License verification is self-hosted on its own domain with a backup download host (agenticwp.pages.dev) and a 7-day grace if it is unreachable. Nothing phones home except the daily license check.

Is it safe to give an AI write access?

Writes go through one audited path: capability check, license, per-post lock, backup, Elementor's own save, element-set verification. Destructive operations require an explicit confirm. The won't-do list (no PHP, no plugin install, no SQL, no users, no shell) is enforced by the plugin, not by prompt.

Try before buying

Install the free build and every read tool works without a key: health report, snapshots, search, catalog, design system. Buy when the first write is due; the agent will tell you.

License portal · manage sites, re-send keys, download the latest build.

FAQ

Questions agencies ask first

What can the AI not do through AgenticWP?
Edit PHP files, install or activate plugins and themes, run SQL, create users, change hosting or server configuration, write files outside the media library. These are enforced in the plugin, not by prompt, and the skill tells the agent to name the right tool (WP Admin, wp-cli, your editor) instead.
Which AI tools does it work with?
Any MCP client: Claude Code, Claude Desktop, Cursor, Windsurf, VS Code Copilot, JetBrains, Zed, Cline, Roo Code, Continue, Aider, Gemini CLI, OpenAI Agents SDK, LangChain, CrewAI, AutoGen and more. The package ships rule files for the common ones and the skill as a folder.
Does it touch the frontend of my site?
No. The plugin registers REST routes only; it adds no hooks that run for visitors. Pages are rendered by Elementor and your theme exactly as before.
Which page builders are supported?
Elementor (classic containers and the Elementor 4 atomic elements, unofficial support), Gutenberg blocks by index path, and the Astra theme settings. Everything else is reachable through the WordPress and WooCommerce REST passthrough. Version 3.15.4 ships 112 tools.
Can I try it before buying?
Yes. Every read tool is free without a key: health report, page snapshots, content search, catalog, design system, broken-link scan, SEO audit. Writes through the Elementor save path, media, menus and bulk products need a license.
What are the requirements?
WordPress 6.0+, PHP 7.4+, Python 3.10+ for the MCP server, an application password for the connecting user (manage_options). Elementor and WooCommerce are optional; the tools detect what is installed.
How do updates work?
Licensed sites see plugin updates in WP Admin like any other plugin. The MCP server checks a signed manifest and can update itself with a backup and rollback. Plugin and server ship in lockstep; the status tool reports version drift.
What is the refund policy?
14 days, no questions. The license is revoked on refund and the plugin falls back to the free read-only tier.
Does it send telemetry?
No. The only outbound request from the plugin is the daily license verification with the key and the site URL. The MCP server talks to your WordPress site and, only when you ask, to Openverse for stock images and the update manifest.