Claude can now read and change WordPress sites through MCP, the open protocol AI agents use to call tools. Here are the ways to connect it in 2026, what each is good for, and how agencies can drive every client site from Claude Code, Cursor or Codex through WPOS.
Until recently, using Claude on a WordPress site meant copying text out of a chat and pasting it into the editor. That changed. WordPress 6.9 added the Abilities API, a standard way for core, plugins and themes to describe what a site can do, and the WordPress project's official MCP Adapter turns those abilities into tools that any MCP client can call. WordPress.com runs an MCP server of its own that self-hosted sites can reach through Jetpack, and more than twenty plugins now ship one too.
The practical result is that claude.ai, Claude Desktop and Claude Code can be connected to a WordPress site and asked to find content, draft and update posts, review comments or check plugins, within whatever permissions you grant. The open questions are no longer whether it works. They are which connection to use, how much access to give, and how to keep a person in charge of what reaches a live site.
There is no single Claude plugin for WordPress. Claude connects through MCP servers, and in 2026 there are five sound places to get one. They differ in where they work, how much they let Claude do, and how much setup they take.
| Option | Works on | What Claude gets | Setup | Best for |
|---|---|---|---|---|
| WordPress.com MCP | WordPress.com sites, and self-hosted sites connected through Jetpack | Read and write tools, with a read-only switch; OAuth 2.1 sign-in | Turn on MCP in your WordPress.com account, then add the connector in Claude | Sites already on WordPress.com or Jetpack |
| Official MCP Adapter | Self-hosted WordPress 6.9 or later | The abilities core, plugins and your theme choose to expose | Install the plugin; connect through WP-CLI locally, or an application password remotely | Developers who want the open, standard route |
| An MCP plugin | Self-hosted WordPress | A ready-made toolset, often hundreds of tools, plus the plugin’s own guardrails | Install it, copy the URL or key it gives you, add it to Claude | Broad tools today without writing code |
| Elementor Ultra | Sites built with Elementor 4 | About 90 Elementor tools for native, editable pages, with validation and rollback | A Claude Code plugin, plus an application password | Developers building Elementor sites from Claude Code |
| WPOS | Any WordPress site with the WPOS plugin, on any host | The same tools WPOS’s built-in agent uses: native Gutenberg, Elementor and Divi builds, media, users, SEO, WooCommerce and read-only inspection | Connect the site to WPOS, then point your MCP client at it | Agencies whose team already works in Claude Code, Cursor or Codex |
Step-by-step setup is in How to connect Claude to WordPress. WPOS is our product, and Elementor Ultra is an open-source project from the WPOS team, documented at docs.wpos.ai/ultra.
WPOS speaks MCP. 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. Driving a site from your own agent doesn’t spend WPOS credits: you pay your own model provider. Site licensing is unchanged, so you license the sites you publish however you operate them. The WPOS plugin stays on each site, because it is what exposes the tools, and each site’s content stays in its own database on its own host.
You can use both: the built-in agent in wp-admin for account managers and designers, your own agent for developers. Start free, then book a free 30-minute call with the founders to connect your MCP client to your first site.
On WordPress.com, or already running Jetpack? WordPress.com's MCP server is the shortest path: OAuth sign-in, read and write tools, and a read-only switch.
Install the official MCP Adapter on WordPress 6.9 or later and expose only the abilities you choose. It is open, auditable and maintained by the WordPress project.
An MCP plugin such as WPVibe, AI Engine or Easy MCP AI gives Claude a large toolset in minutes. Choose on authentication and guardrails, not on tool count.
Use Elementor Ultra with Claude Code for native, editable Elementor 4 pages. For many client sites across builders and hosts, use WPOS, from its built-in agent or from your own Claude Code, Cursor or Codex.
Connecting Claude gives an agent tools. Running a client book takes a workspace, house rules and a review step.
Connect each client site to your WPOS workspace and work on it from the built-in agent in wp-admin or from your own Claude Code, Cursor or Codex, on the host the client already pays for.
Pages land as normal Gutenberg, Elementor or Divi content your designers can open and edit by hand afterwards.
Write conventions once as skills, such as brand rules, layout patterns and QA checklists, and the built-in agent reads them before it works on any site.
The built-in agent takes a browser screenshot of its own work and checks the render before it reports a build finished.
Products, variations, stock, orders, coupons and reports go through WooCommerce's own APIs, not straight into the database.
The Partner Program lets agencies resell WPOS under their own brand, with a password-protected client handoff.
Straight answers on connecting Claude to a WordPress site, and where WPOS fits.
Yes, once it is connected through MCP. Sites on WordPress.com, and self-hosted sites connected through Jetpack, can use WordPress.com's MCP server, which offers read and write tools with a read-only option. Other self-hosted sites can use the official MCP Adapter, an MCP plugin or WPOS. What Claude can change depends on the tools exposed and the permissions of the WordPress user it connects as.
Yes. The MCP Adapter is the WordPress project's official plugin. It turns abilities registered through the Abilities API, added in WordPress 6.9, into MCP tools. Abilities are private by default, so a site exposes only what a developer opts in.
For custom connectors in claude.ai and Claude Desktop, Anthropic lists Pro, Max, Team and Enterprise, with Free accounts limited to one custom connector. In Claude Code, MCP servers are added from the terminal with the claude mcp add command.
It can be, if you treat Claude like any other account with access. Connect it as a dedicated user with only the capabilities the job needs, start read-only, try new kinds of task on staging, use OAuth or application passwords you can revoke, and keep a person approving anything clients will see.
It depends on the server. Some MCP plugins add page-builder tools; many only handle posts, pages and settings. For Elementor 4, the open-source Elementor Ultra project from the WPOS team gives Claude Code about 90 Elementor tools. WPOS builds natively in Gutenberg, Elementor and Divi, from its own agent or from yours.
Yes. WPOS speaks MCP, so Claude Code, Cursor, Codex or any MCP client can drive the same tools as WPOS's built-in agent: building pages in Gutenberg, Elementor or Divi, managing media, users, SEO and WooCommerce, and reading the site safely. The WPOS plugin stays on each site, and your own agent doesn't spend WPOS credits.
A workspace for running many client sites. Work through the built-in agent in wp-admin or bring your own agent over MCP; either way the work lands natively in each site's builder, bad changes can be undone with per-page backups and widget revisions, and clients can get a white-label handoff.
Free for 30 days with 5,000 credits, a live site plus a staging sandbox, and no card. After that it is $25 per site, dropping to $19.50 as you add sites. Credits pay for work done by WPOS's own agent; driving a site from your own agent over MCP doesn't use them.
Go deeper on Claude and WordPress:
From WPOS's agent in wp-admin or from your own Claude Code. Free for 30 days: 5,000 credits, a live site plus a sandbox, no card.
Start free