To connect Claude to a WordPress site, install the official MCP Adapter plugin, create an application password, and point Claude at your site’s MCP address: /wp-json/mcp/mcp-adapter-default-server. Claude then sees three tools it can use to find and run any WordPress “ability” that a plugin has made available to AI. We connected our own site, nowdigiverse.com, to Claude Code this way on 7 November 2026. This guide shows the steps and what Claude could actually do once connected.
What is the WordPress MCP Adapter?
The MCP Adapter is the official WordPress package for the Model Context Protocol, part of the AI Building Blocks for WordPress initiative. It takes abilities, which are actions that WordPress core and plugins register through the Abilities API, and serves them as MCP tools, resources and prompts. Any MCP client can then use them: Claude Code, Claude Desktop, Cursor or VS Code. New to MCP? Start with what an MCP server is.
The important design choice is that abilities are private by default. An ability only reaches MCP when the plugin that registers it marks it public, and every call still runs that ability’s own WordPress permission check as the signed-in user.
What do you need before you start?
- A WordPress site with the Abilities API, which is part of core since WordPress 6.9.
- HTTPS. WordPress only offers application passwords over HTTPS, apart from local development sites.
- An administrator account to install the plugin, plus the account Claude will sign in as (see step 3).
- Claude Code or Claude Desktop. For Claude Desktop you also need Node.js, because it connects through a small proxy run with
npx.
How do you connect Claude to WordPress, step by step?
Step 1: Install the MCP Adapter
In WordPress go to Plugins → Add New, search for MCP Adapter, then install and activate it. You can also get it from the GitHub repository.
Some plugins ship their own copy of the adapter. On our site the MCP address already answered before we activated the standalone plugin, because another plugin had brought it along. To check yours, open https://yoursite.com/wp-json/ and look for mcp in the list of namespaces.
Step 2: Know your server address
The adapter creates a default server automatically. Its address is:
https://yoursite.com/wp-json/mcp/mcp-adapter-default-serverOpening it in a browser is not a useful test. The server only answers MCP requests from a signed-in user, and plain GET requests return 405 Method Not Allowed because streaming over GET is not implemented yet. Step 5 shows a proper test.
Step 3: Create an application password for a limited user
Go to Users → Profile → Application Passwords, enter a name such as Claude Code, click Add Application Password and copy the password. WordPress shows it only once.
Think about which user you create it for. The default server only needs the read capability to connect, but each ability then checks the user’s own permissions. On our site, WooCommerce exposes abilities to update order statuses and to create, update and delete products. A user who can’t delete products in wp-admin can’t delete them through Claude either, so a dedicated account with only the role Claude needs is the safest set-up.
Step 4: Add the server to Claude
Claude Code can talk to the server directly over HTTP. Encode your username and application password, then add the server with an Authorization header:
AUTH=$(printf '%s' "your-username:xxxx xxxx xxxx xxxx xxxx xxxx" | base64)
claude mcp add --transport http wordpress \
https://yoursite.com/wp-json/mcp/mcp-adapter-default-server \
--header "Authorization: Basic $AUTH"This stores the header in Claude Code’s configuration, so the password sits on your computer in plain text. That is normal for MCP clients, but it is one more reason to use a limited account. On our own set-up we went a step further: a small local bridge script passes requests to the site with curl, reading the credentials from a file that only curl opens, so the password never appears in Claude’s config at all.
Claude Desktop launches local servers, so the adapter’s documentation uses Automattic’s @automattic/mcp-wordpress-remote proxy. Add this to the file that opens from Settings → Developer → Edit Config:
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": [
"-y",
"@automattic/mcp-wordpress-remote@latest"
],
"env": {
"WP_API_URL": "https://yoursite.com/wp-json/mcp/mcp-adapter-default-server",
"WP_API_USERNAME": "your-username",
"WP_API_PASSWORD": "your-application-password"
}
}
}
}Local sites don’t need HTTP at all. If WP-CLI is installed, the client can start the server directly over standard input and output:
{
"mcpServers": {
"wordpress": {
"command": "wp",
"args": [
"--path=/path/to/your/wordpress/site",
"mcp-adapter",
"serve",
"--server=mcp-adapter-default-server",
"--user=admin"
]
}
}
}Change --user to the account whose permissions Claude should have.
Step 5: Test the connection
- Restart Claude, or run
claude mcp listin Claude Code to see whether the server connected. - Ask Claude: “Which WordPress tools do you have?” It should list three:
mcp-adapter-discover-abilities,mcp-adapter-get-ability-infoandmcp-adapter-execute-ability. - Ask: “Discover the abilities available on my site.” Claude calls the first tool and lists every public ability.
- Run something read-only first, for example “Get the site information.”, before you let it change anything.
Why does Claude only see three tools?
The default server uses layered discovery. Instead of sending Claude the full description of every ability up front, it offers three meta-tools: one to list the public abilities, one to read a single ability’s inputs, and one to run it. However many abilities your plugins add, Claude’s tool list stays at three, which keeps the context small. Claude simply makes an extra call or two to find the right ability before it runs it.
What can Claude do once it is connected?
That depends entirely on your plugins. When we asked our own server on 7 November 2026, it reported 42 public abilities:
| Source | Abilities | Examples |
|---|---|---|
| Rank Math SEO | 29 | Audit and fix site SEO, read a post’s SEO meta and schema, link reports, top keywords |
| WooCommerce | 7 | Query orders, add an order note, update order status, query, create, update and delete products |
| WordPress core | 3 | Get site information, user information and environment information |
| GTM Kit | 3 | Read the Google Tag Manager configuration, consent status and tracking health |
None of these were switched on by us. Each plugin decided which of its abilities to make public. That is why it is worth running the discover step yourself after you connect, so you know exactly what an AI client can reach on your site.
How do you expose your own abilities to Claude?
If you build plugins, register an ability and set meta.mcp.public to true. (Setting meta.public makes it public to all clients, including MCP; an explicit meta.mcp.public => false keeps an otherwise public ability out of MCP.) Always give it a real permission check:
wp_register_ability( 'my-plugin/get-open-quotes', array(
'label' => 'Get open quotes',
'description' => 'Lists quote requests that are still open.',
'category' => 'site',
'execute_callback' => 'my_plugin_get_open_quotes',
'permission_callback' => function () {
return current_user_can( 'edit_posts' );
},
'meta' => array(
'mcp' => array( 'public' => true ), // expose over MCP only
),
) );The adapter checks three things before running it: the user is signed in, they have the capability the server requires (read by default, changeable with filters), and the ability’s own permission_callback passes.
What errors might you see?
| Error | What it means | Fix |
|---|---|---|
400 Missing Mcp-Session-Id header | A request was sent before the client started a session | Use a real MCP client, or send initialize first and reuse the session ID it returns. |
401 User not authenticated | The username or application password was wrong, or never reached WordPress | Create a new application password, rebuild the base64 string, and check that the site uses HTTPS. Some server set-ups drop the Authorization header; your host can confirm. |
| 405 on GET | Streaming over GET is not implemented yet | Nothing to fix; MCP clients use POST. |
| Claude connects but finds no abilities | No plugin on the site has marked an ability public, or the user lacks the capability | Run the discover tool and check the user’s role. |
One lesson from our own bridge: after we switched to the standalone MCP Adapter plugin, requests after the first one also needed the MCP-Protocol-Version header, which the MCP specification asks clients to send. Official clients already do this. It only matters if you write your own client or proxy.
MCP Adapter or an MCP plugin: which do you need?
Start with the MCP Adapter if you only need what your plugins already expose. Choose an all-in-one MCP plugin if you want Claude to manage posts, WooCommerce or a page builder without writing abilities yourself. The adapter shows Claude less, and that is often what you want.
| Option | What it gives Claude | Active installs* | Pick it when |
|---|---|---|---|
| MCP Adapter (WordPress) | Turns abilities your plugins register into MCP tools. Only abilities marked public are shown. | 70,000+ | You want the official route and only what your plugins expose |
| AI Engine (Meow Apps) | MCP server plus an AI chatbot. Lists more than 140 tools, including posts, page builders, SEO fields and WooCommerce. | 90,000+ | You want a large ready-made tool set and a chatbot in one plugin |
| Flex MCP (StifLi) | 122+ built-in WordPress and WooCommerce tools, OAuth 2.1 sign-in for MCP clients, and undo for tracked changes. | 900+ | You want OAuth instead of application passwords, and an undo |
| EMCP Tools | Hundreds of tools on top of the adapter, focused on building Elementor pages. | n/a | Your site is built with Elementor |
On our own site we use the MCP Adapter with a read-only user, because Claude only needs to read SEO fields. For Elementor page building we add EMCP Tools; our Elementor MCP plugin setup guide covers that route. Whichever you pick, install only one MCP server per site, so you know which tools Claude can call.
Is it safe to connect Claude to WordPress?
It is safe enough if you limit what the connection can do. Claude can only act as the WordPress user you connect, so give that user the lowest role the job needs, expose only the tools you use, and test on a staging copy first. The risk grows with every write tool you switch on.
The MCP specification itself warns that tools represent arbitrary code execution and that tool descriptions should be treated as untrusted unless the server is trusted (MCP specification, security section). For WordPress, that turns into a short checklist:
- Use a separate user. Create one for the AI connection with the lowest role that works (Author or Editor for content, never Administrator unless you must).
- Use one application password per app. You can revoke each one on its own under Users → Profile, without changing your login (WordPress application passwords guide). If your plugin supports OAuth, as Flex MCP does, that works too.
- Expose only what you need. With the MCP Adapter, only abilities marked public reach Claude. With an all-in-one plugin, switch off the tool groups you don’t use.
- Keep approval on. Let Claude ask before each tool call, at least until you trust the setup. The MCP specification requires clients to get the user’s consent before a tool runs.
- Watch what Claude reads. Comments, form entries and imported content can contain instructions aimed at the AI (prompt injection). Don’t let an agent with write access act on them unattended.
- Back up and test on staging. Try new write tools on a copy of the site, and keep a recent backup before you let an agent change content or orders.
For a plain-English overview of how MCP works and where the risks come from, read what an MCP server is.
Frequently asked questions
Is the MCP Adapter an official WordPress project?
Yes. It is the official WordPress package for MCP integration, developed in the WordPress GitHub organisation as part of the AI Building Blocks for WordPress initiative.
Can Claude change my site through the MCP Adapter?
Only through abilities that a plugin has made public, and only if the connected user is allowed to do the same thing in wp-admin. Some public abilities do write, such as WooCommerce’s product and order abilities, so connect with a limited account.
Does it work with Cursor or VS Code too?
Yes. Any MCP client can connect. The adapter’s documentation mentions Claude Desktop, Claude Code, VS Code and Cursor, either directly over HTTP or through the mcp-wordpress-remote proxy.
Do I need to write code?
No, not to connect. You install a plugin, create an application password and add one config entry to Claude. You only write code if you want to expose your own abilities.
Want help connecting AI to your site?
We build MCP connections and AI features for WordPress and WooCommerce sites, from content and SEO workflows to order handling. See our AI solutions service or tell us what you want to automate. If you add an AI chatbot to your site, see what the EU AI Act says it must disclose.
Sources: WordPress MCP Adapter README, Default MCP Server guide and CLI Usage guide; Claude Code claude mcp add --help; our own server, queried on 7 November 2026. Checked 7 November 2026. Nowdigiverse is not affiliated with WordPress.org, Automattic or Anthropic.