Can Claude or ChatGPT Manage WordPress? What Works Where
Can Claude manage your WordPress site? What works on claude.ai, Claude Desktop, Claude Code and ChatGPT, and why the MCP Adapter fails on the web.
Yes, but which route works depends on two things: where your site is hosted, and which app you use. Claude.ai in the browser, Claude Desktop, Claude Code and ChatGPT each connect in slightly different ways, and the official WordPress MCP Adapter doesn’t work with the two web apps on its own.
We did not test every connection ourselves. This guide is built from the vendors’ own documentation and from a hands-on test WPShout published on 28 October 2026. Where a vendor’s page does not say something, we say so rather than guess.
Can Claude manage my WordPress site?
Yes. Claude connects to WordPress through MCP (Model Context Protocol, an open standard that lets an AI app use tools on another service). What it can do depends on the route: the WordPress.com connector, the official MCP Adapter plugin, a WordPress plugin that runs its own MCP server, or a hosted service that covers many sites.
“Manage” also means different things. Reading your posts and plugin list is one level. Editing a draft is another. Updating plugins on a live shop is a third, and that is where the safety controls in each route matter most.
What are the ways to connect Claude or ChatGPT to WordPress?
There are four routes worth knowing in November 2026.
| Route | What it is | Works for | Sign-in |
|---|---|---|---|
| WordPress.com connector (also used by Jetpack) | Automattic’s hosted MCP server at public-api.wordpress.com/wpcom/v2/mcp/v1 | Sites on WordPress.com, and self-hosted sites connected through the Jetpack plugin | OAuth 2.1 in the browser |
| MCP Adapter | The official WordPress.org plugin that turns a site’s registered “abilities” into MCP tools | Any self-hosted site on WordPress 6.9 or newer | Application Password (a revocable password for apps, made under Users > Profile) or WP-CLI |
| Plugins with their own MCP server | Plugins that run an MCP server inside your site, such as Easy MCP AI | Any self-hosted site where you install them | Varies by plugin. WPShout’s Easy MCP AI test used an API key |
| Hosted fleet services | A service that already connects to many of your sites and exposes them over MCP, such as TalkToWP or Modular DS (or MainWP’s local server) | Agencies and owners with several sites | OAuth (hosted ones) or an Application Password (MainWP) |
The WordPress.com route is the shortest if you already use Jetpack. A Jetpack-connected self-hosted site uses the same MCP server as a site hosted on WordPress.com, and one connection reaches every site on that WordPress.com account (WordPress.com developer docs).
Which route works on claude.ai, Claude Desktop, Claude Code and ChatGPT?
| Route | claude.ai (web) | Claude Desktop | Claude Code | ChatGPT |
|---|---|---|---|---|
| WordPress.com / Jetpack | Yes: add the WordPress.com connector and sign in | Yes: through the built-in Connectors Directory | Yes: add the server URL as an HTTP MCP server, then sign in | Yes: through WordPress.com’s ChatGPT plugin, per its docs |
| MCP Adapter on its own | No. The adapter has no OAuth server, and the web app expects OAuth | Yes, through the @automattic/mcp-wordpress-remote helper with an Application Password (needs Node.js on your computer) | Yes, with an Application Password | No. It has no OAuth server |
| Plugin with its own MCP server | Depends on the plugin. Web apps expect OAuth, so check its documentation | Check the plugin’s documentation | Check the plugin’s documentation | Check the plugin’s documentation |
| TalkToWP (hosted, many sites) | Yes: listed in Claude’s Connectors Directory, OAuth sign-in | Yes | Yes | Works as a custom MCP connector; which ChatGPT plans can add one is set by OpenAI (see its help page) |
Sources for the table: Jetpack and WordPress.com docs for the first row (Jetpack), WPShout’s tested guide and the adapter’s GitHub issue for the MCP Adapter row (WPShout), and TalkToWP’s MCP page with its Claude directory listing.
Two client details matter here. Claude.ai custom connectors sign in with OAuth by default. A request-header option (which could carry a password or key) exists, but Claude’s documentation calls it a beta available to a limited set of organizations (Claude docs). On ChatGPT, OpenAI’s help page says custom MCP server connections and full MCP support are available for Business and Enterprise/Edu customers on ChatGPT web, and that custom MCP servers can’t be connected on mobile (OpenAI). Check that page for your own plan before you plan around ChatGPT.
Can claude.ai connect to a self-hosted WordPress site?
Yes, if the site is connected to WordPress.com through Jetpack, or runs a plugin with an OAuth sign-in, or is covered by a hosted service that signs in with OAuth. The official MCP Adapter on its own will not work with claude.ai in the browser, because it has no OAuth sign-in.
The Jetpack route, from Jetpack’s support page (last updated 9 November 2026):
- MCP access is included with the Jetpack AI and Jetpack Complete plans. Sites on the free plan can connect an agent through 30 November 2026.
- You add the WordPress.com connector in Claude, sign in with the WordPress.com account the site is connected to, and approve.
- You choose what agents can read and write, by group: content authoring, site editing, plugin management and so on. Write access to plugin management covers searching, installing, updating, activating and removing plugins.
- There is an activity log of what agents did.
When you approve the connection, WordPress.com asks for an access level: full access, or read only (WordPress.com developer docs). Read only is the sensible first choice.
If you don’t want Jetpack, a plugin with OAuth sign-in is the other route for the web app. Check the plugin’s documentation for OAuth before you install it. WPShout tested Easy MCP AI (made by Themeisle, the company behind WPShout, which they disclose) with an API key bound to an administrator, and it edited a draft post where the adapter could not.
Why is the WordPress MCP Adapter not working with Claude?
Because claude.ai signs in to custom connectors with OAuth, and the MCP Adapter has no OAuth server. It expects a logged-in WordPress user, normally through an Application Password. So the browser app can’t sign in, even when the URL is right.
The usual error looks like this: “Your account was authorized, but no MCP server was found at the provided URL.” That message is the title of GitHub issue #361 on the adapter’s repository, opened on 1 October 2026 and still open when we checked in November 2026. A reply on the issue explains that the adapter’s HTTP endpoint only checks that the caller can read, and that the documented way to connect a remote client is the @automattic/mcp-wordpress-remote helper with an Application Password, which works for Claude Desktop and Claude Code. The adapter’s own guide says the web apps “cannot connect to MCP Adapter on their own today” (as quoted by WPShout).
WPShout’s test on 28 October 2026 matched this. Pointing a claude.ai custom connector at the adapter failed with a message about not being able to register with the site’s sign-in service, and the site log showed 404 errors on the OAuth discovery paths.
If you are stuck, these three checks come from the replies on issue #361:
- Is the endpoint there? Send a POST request to
https://example.com/wp-json/mcp/mcp-adapter-default-server. A 401 means the route exists and wants a login (expected). A 404 means the plugin is inactive, the URL is wrong, or the site uses plain permalinks. HTML or a redirect means a security or caching layer is intercepting/wp-json/. - Is the URL in Claude the full endpoint, not just your domain?
- Did WordPress see a user? With
WP_DEBUG_LOGon, a line saying user ID 0 means the request arrived but WordPress didn’t accept the token as a login.
If you only need Claude Desktop or Claude Code, the adapter works today with an Application Password. If you need claude.ai or ChatGPT in the browser, use one of the other routes.
There is a second surprise once you do connect. On WordPress 7.1, WPShout’s test of a fresh adapter install found three abilities, all read-only: site info, user info and environment info. WPShout’s check of core code says that on 6.9 and 7.0 none are public, so the list starts empty. WPShout asked Claude Code to edit a draft over the adapter and it couldn’t, because no ability on the site could list or edit posts. Write abilities come from plugins that register them. The adapter is version 0.7.1, has 50,000+ active installs, and the project calls itself experimental (WPShout).
Which route should you pick?
| Your situation | Route that fits |
|---|---|
| One site, already on WordPress.com or using Jetpack, want claude.ai or ChatGPT | WordPress.com connector |
| One self-hosted site, no Jetpack, want claude.ai in the browser | A plugin with OAuth sign-in |
| You build plugins and want to expose your own abilities to AI | MCP Adapter, with Claude Desktop or Claude Code |
| You work in Claude Code and are happy with Application Passwords | MCP Adapter or a plugin; both work |
| Many client sites, want monitoring data and maintenance in one connection | A hosted fleet service (TalkToWP, Modular DS) or MainWP’s local MCP server |
For the many-sites case, we compare the options in detail in WordPress MCP servers for multiple sites, compared.
What WordPress itself has shipped for AI
Dated items only:
- July 2025: the Core AI team announced “AI Building Blocks for WordPress”, including the Abilities API and the MCP Adapter (make.wordpress.org/ai).
- WordPress 6.9: the Abilities API shipped in core, a way for plugins, themes and core to describe what they can do in a form machines can discover (make.wordpress.org/core).
- February 2026: the WordPress Developer Blog introduced the MCP Adapter for Claude Desktop, Claude Code and Cursor (developer.wordpress.org).
- 7 October 2026: the MCP Adapter became a canonical plugin in the WordPress.org directory, kept out of core for now because MCP is still changing (make.wordpress.org/ai).
- 29 October 2026: the AI plugin 1.5.0 added an “MCP Access” screen where site owners choose which abilities AI agents can see (make.wordpress.org/ai).
The direction is consistent: access that the site owner exposes on purpose, one ability at a time.
How do you let an AI change WordPress safely?
Start read-only and add write access one type at a time. Routes differ in how they let you do this: WordPress.com and Jetpack have read and write groups, MainWP has a confirmation step for destructive operations, and TalkToWP is read-only until the owner allows a type of change.
A few rules apply whatever route you choose:
- Connect as a dedicated WordPress user with the lowest role that can do the job, not your own administrator account.
- Create one Application Password per app, so revoking one doesn’t break the others.
- Treat what the AI reads as untrusted. A comment or an imported post can contain instructions aimed at the AI (this is called prompt injection).
- Know what can be undone. Most routes can change your live site the same way wp-admin can, and not every change has an undo.
TalkToWP is an example of how narrow the undo can be. Its MCP server takes a snapshot before a plugin or theme update, checks the site afterwards and restores the snapshot automatically if the site breaks. WordPress core updates cannot be snapshotted or reverted, and file writes through its write_site_file tool are not snapshotted either. It does not run backups, so you still need a backup tool. It applies an update only when you or your AI ask, after you confirm. Other routes have their own limits; check them before you grant write access. You can read the full list on TalkToWP’s MCP page, and the free plan gives read-only access to your first site.
For the checks to do before any plugin update, AI-driven or not, see how to know if a plugin update is safe. If you run client sites, the agency maintenance checklist shows where this fits.
Frequently asked questions
Can Claude manage my WordPress site?
Yes, through MCP. On claude.ai you need a route with OAuth sign-in: the WordPress.com connector (for WordPress.com or Jetpack sites), a plugin with OAuth, or a hosted service. Claude Desktop and Claude Code can also use the official MCP Adapter.
How do I connect claude.ai to a self-hosted WordPress site?
Either connect the site to WordPress.com with Jetpack and add the WordPress.com connector in Claude, or install a WordPress plugin that offers OAuth sign-in and add it as a custom connector. The MCP Adapter alone won’t work in the browser.
Why is the WordPress MCP Adapter not working with Claude.ai?
The adapter has no OAuth server, and claude.ai custom connectors sign in with OAuth. The typical error says your account was authorized but no MCP server was found at the URL. Use Claude Desktop or Claude Code with an Application Password, or another route.
Can ChatGPT connect to WordPress?
Yes, through WordPress.com’s ChatGPT plugin for WordPress.com and Jetpack sites, per its docs. OpenAI’s help page says custom MCP server connections are available for ChatGPT Business and Enterprise/Edu customers on ChatGPT web; check that page for your own plan.
Does the MCP Adapter let Claude edit posts?
Not out of the box. On WordPress 7.1, WPShout found it exposes three read-only core abilities. Editing needs plugins that register write abilities.
Is it safe to give an AI write access to WordPress?
It can be, if you start read-only, use a low-role user, grant one type of change at a time and know which changes can be undone. Keep a separate backup tool whatever route you use.