Compare

WordPress ships a transport. You still hit publish.

The official MCP Adapter is a free pipe. WP Adapter is the shop on top — landings, copy, CSS, catalog — inside the Elementor and Divi you paid for. Claude talks to wpadapter.com/mcp.

Get started

Not official WordPress Draft-only Elementor + Divi Undo any change

The dock is on WordPress. The connector is not.

The address every model uses

wpadapter.com/mcp

Never your WordPress URL. Never an Application Password.

The competitor is a transport

Free pipe. Paid bureau.

WordPress ships three read-only abilities and a plugin that turns public abilities into MCP. You buy WP Adapter because publish stays yours, and the layout you paid for stays put.

Official adapter, out of the box

of 14

WP Adapter

of 14

Official WordPress

MCP Adapter

GPL plugin · not in core · free

A pipe. Three read-only core abilities. HTTP on your origin. The AI is a WordPress user — often Administrator.

No Elementor / Divi patch
No draft lock
No signed preview
No rollback

WP Adapter

14 jobs the pipe does not do

€79 / year

5 WordPress sites · Pro

Cloud MCP. Dedicated editor. Draft-only. Snapshot first. The zip is a dock.

Canvas stays
You hit publish
Preview the draft
Undo any change

Do not mix these up

Four things called WordPress MCP.

Mixing them up is how people paste an Administrator password into Claude.

Core 7.1.3

Abilities API

In WordPress since 6.9

Read-only: get-site-info, get-user-info, get-environment-info. No create or update post.

Separate plugin

Official adapter

Not in core

Three meta-tools. Then whatever other plugins marked public. HTTP on your WordPress, or WP-CLI as a user.

Hosted only

WordPress.com

Paid WP.com / Jetpack AI

Posts, pages, comments, users, stats. Gutenberg. Not Elementor or Divi. The agent can publish, delete, invite, change roles.

This product

WP Adapter

Not official. On purpose.

Curated tools. Cloud MCP. Draft-only. Canvas-aware. Rollback. No public origin connector.

Side by side

14 crosses. 14 ticks.

Out of the box the official adapter is a pipe. WP Adapter is the bureau. Count them.

The job Official adapter WP Adapter

Cloud MCP URL Your WordPress /wp-json/mcp Always wpadapter.com/mcp

No Application Password Application Password, often admin OAuth or Bearer. Origin is HMAC

Dedicated non-admin agent The AI is a WordPress user wp-adapter-agent. Never Administrator

Create and update posts Not in core. Another plugin must opt in create-post / update-post, draft by default

You still hit publish Whatever that user can do Origin Policy. Cloud cannot override it

Elementor, Divi, Bricks patch A post_content write wrecks the canvas mode=patch keeps the layout you paid for

Signed draft preview Public slug 404s preview-post — visitor URL, 24 hours

CSS fight tools No search-css, inspect-front, update-site-css

Snapshot and rollback No snapshot. No denylist Snapshot before every mutate. rollback

WooCommerce catalog Not in core Products, stock, orders — drafts until you allow live

Forms on your Stripe No Separate zip. Your Stripe. You hit live

Several WordPress sites One origin per connector Org roster. Agency client keys lock to one site

Customer never sees wp-admin They get a WordPress login Hand them Claude. Never wp-admin

Audit log Whatever you built Origin Activity + cloud usage

The canvas is the product

Patch the layout you already paid for.

A naive post_content write wrecks builder JSON and shortcodes. Default mode=patch keeps the page. Unknown builders are detected and not flattened. Theme PHP is never edited.

Gutenberg
Classic
Elementor
Divi 4
Divi 5
Bricks
Beaver
WPBakery
Breakdance
Oxygen

Safety, one line each

Who the agent is.

Official adapter

The AI is a WordPress user. If that user is Administrator, publish is theirs.

WordPress.com

The AI is your account. It can publish, delete, invite, and uninstall plugins.

WP Adapter

The AI is a non-admin editor. Draft-only. Dangerous tools off. Snapshot first. You still hit publish.

Never

eval, theme PHP, SQL, zip upload, create_user, force-delete, a public origin MCP server, or an Application Password on the cloud path. Plugin install is a wordpress.org slug, and only when you turn that on.

When to use which

Pick the pipe that matches the job.

Official adapter

Local WP-CLI. Read site info. Expose your plugin’s abilities.

WordPress.com

A WP.com / Jetpack blog. Gutenberg, stats, comments.

WP Adapter

Self-hosted Elementor or Divi. Copy, landings, CSS. Customer never sees wp-admin.

Don’t

Paste Administrator into Claude — and accept that publish is theirs.

We do not do comments, users, stats, domains, or billing. We do not auto-discover every other plugin’s abilities. This is a curated bureau, not a generic gateway.

The questions people actually ask

Not official. On purpose.

Is WP Adapter the official WordPress MCP Adapter?

No. WordPress ships a free MCP transport and three read-only core abilities. WP Adapter is a product on top: curated tools, origin Policy, canvas-aware edits, rollback, and a cloud MCP at wpadapter.com. We are not affiliated with, endorsed by, or owned by the WordPress Foundation.

Does WordPress core include MCP?

WordPress 6.9+ includes the Abilities API. The official MCP Adapter is a separate plugin. Out of the box, core exposes three read-only abilities: site info, user info, and environment info. It does not create or update posts.

Can the official WordPress MCP Adapter edit Elementor or Divi?

No. The official adapter is a transport. A naive post_content write wrecks builder JSON and shortcodes. WP Adapter patches copy inside Elementor, Divi 4, Divi 5, Bricks, Beaver Builder, WPBakery, Breakdance, and Oxygen. A new Divi landing is native [et_pb_section] shortcodes — still a draft.

Does WP Adapter use Application Passwords?

Not on the cloud path. Claude, ChatGPT, Cursor, and Grok talk to https://wpadapter.com/mcp. The plugin on WordPress is an HMAC dock. The runtime user is wp-adapter-agent, not Administrator.

User manual Safety