WordPress MCP Server: Connect Claude to Your Site Without Giving Away the Keys
Yes, WordPress has official routes for connecting an AI assistant. WordPress.com runs a built-in MCP server that signs you in with OAuth, and the WordPress project publishes an official MCP Adapter plugin for self-hosted sites. Which one fits depends on where your site lives. Whichever you choose, the safe approach is the same: give the assistant the narrowest access you can. Try it on a copy of your site first. Keep a person in charge of anything that publishes or deletes.
This is general information, not security advice. Details come from WordPress.com’s developer documentation, the WordPress MCP Adapter README, the WordPress Abilities API handbook and the application passwords guide, read on 6 November 2026. We describe what these documents say. We have not tested these connections on a live site, so treat our suggestions as cautious defaults rather than proven results.
Key Takeaways
- WordPress.com has a built-in MCP server using OAuth 2.1, and its sign-in screen lets you choose Full access or Read only.
- For self-hosted sites, the official route is the WordPress MCP Adapter, which exposes “abilities” that developers opt in, and abilities are private by default.
- Application passwords are a separate WordPress feature that lets an app log in without your real password. You can revoke one at any time.
- Use a separate low-privilege user, try a staging copy first, and keep backups.
Which WordPress Are You Using?
The first question is which WordPress you have, because the options differ.
| Your setup | Official route | Sign-in | Skill needed |
|---|---|---|---|
| Site hosted on WordPress.com | Built-in WordPress.com MCP server | OAuth 2.1 in your browser | Low |
| Self-hosted site connected with Jetpack | Same WordPress.com MCP server | OAuth 2.1 | Low to moderate |
| Self-hosted site, no Jetpack | WordPress MCP Adapter plugin plus abilities | Depends on how it is set up | Developer |
If you are not sure, look at your address bar when you log in. A site you log into at wordpress.com is hosted there. A site you log into at your own domain’s /wp-admin is self-hosted.
Option 1: The WordPress.com MCP Server
WordPress.com’s documentation says it includes a built-in MCP server at https://public-api.wordpress.com/wpcom/v2/mcp/v1. One connection reaches every site on your account. It works on every WordPress.com site, free or paid, and self-hosted sites connected through the Jetpack plugin use the same server.
Setup, per the documentation:
- Enable MCP in your WordPress.com account settings.
- Add the server URL to your AI app. Claude Desktop uses its built-in Connectors Directory, and Claude Code uses
claude mcp add --transport http wpcom-mcpfollowed by the URL. - Your browser opens the WordPress.com authorisation page. Log in, choose an access level and click Allow.
The access level is the important part. WordPress.com offers Full access, which turns on every read and write tool, or Read only, which turns off every write tool. The documentation also notes that this choice rewrites your account-level tool settings, shared by every connected client. A later connection can therefore change what an earlier one can do. Start with Read only.
You can disconnect at any time under Security, then Connected applications. WordPress.com says disconnecting from inside your AI app does not remove its entry there, so check the list and disconnect each entry.
Option 2: The Official MCP Adapter for Self-Hosted Sites
The WordPress MCP Adapter describes itself as “the official WordPress package for MCP integration”. It exposes WordPress “abilities” as MCP tools, resources and prompts. Abilities come from the Abilities API, which per its handbook page is available on WordPress 6.9 and above.
What this means for an owner:
- An ability is a defined action with a name, input and output rules and an optional permission check.
- The adapter’s README says abilities are private by default. A developer has to mark one as public before it is exposed.
- The adapter can be reached over HTTP at
/wp-json/mcp/mcp-adapter-default-serveror through WP-CLI. - Its README lists granular permissions: transport authentication per server and permission checks per ability.
In plain terms, this route is built by developers for developers. Nothing is exposed until someone deliberately chooses to expose it. That is good for safety, but you will likely need a developer or a plugin that registers abilities for you. If that is not you, option 1 or a decision to skip MCP is the sensible choice.
What Are Application Passwords?
You may see “application password” in guides about connecting tools to WordPress. This is a separate WordPress feature, not an MCP feature. WordPress’s guide describes it as a way for an application to log in using a generated password instead of your real one. It is meant for programs, not for people logging in interactively.
Facts from that guide worth knowing:
- Each user can generate and revoke application passwords from their Edit User page.
- By default the feature is available on sites served over HTTPS.
- Credentials are passed to the REST API over
https://using basic authentication. - WordPress stores data on each password’s last use, such as date and IP address, and you can revoke one if you stop trusting it.
If a community MCP server asks for a WordPress username and application password, remember what you are handing over: whatever that user can do. Never create one for an administrator account for this purpose.
A Safe Setup Checklist
These steps are our suggestions based on the documentation, not a vendor guarantee.
- Copy your site first. Test on a staging or local copy, not your live site.
- Take a full backup before connecting anything that can write.
- Use a separate user with the lowest role that works. An Editor or Author can do far less damage than an Administrator. Create the user just for this purpose.
- Choose read-only access if you can. On WordPress.com, pick Read only at the sign-in screen.
- Keep approval prompts on in your AI app so you see each action before it runs.
- Review drafts, do not auto-publish. Let the assistant create drafts and let a person press Publish.
- Do not combine servers casually. An assistant that also reads email or web pages can be steered by hidden text. Keep your WordPress connection separate from tools that read untrusted content.
- Revoke when finished. Remove application passwords or connected apps you no longer use.
What Tasks Make Sense?
| Task | Stance | Why |
|---|---|---|
| “List my last 10 posts and their categories” | Reasonable, read-only | Low impact |
| “Draft an outline for a new post” | Reasonable | Stays as a draft |
| “Find posts missing a meta description” | Reasonable, read-only | Review before changing |
| “Update all my post titles” | Think twice | Bulk edits are hard to undo |
| “Publish this post” | Think twice | Keep a person pressing Publish |
| “Install or change plugins and themes” | Avoid | Can break or expose the site |
| “Delete posts, users or media” | Avoid | Hard to undo |
What Can Go Wrong
The MCP specification says tools “represent arbitrary code execution and must be treated with appropriate caution”. For a website, the realistic problems are over-broad access (an administrator login handed to a tool), bulk changes made on a misunderstood request, and a leaked credential. A staging site, a restricted user and backups cover most of the damage from the first two. Our guide to MCP servers for small business covers the wider risks. The same pattern for another agent tool is in our post on whether OpenClaw is safe for business.
Is This Too Technical?
For WordPress.com, setup is mostly clicking through a sign-in screen. For self-hosted sites the official route expects a developer. If that is not your situation, you can use your AI assistant without a live connection by pasting drafts into WordPress yourself. For accounting tools, see how the same idea works in our QuickBooks and Xero MCP guide, or browse the official MCP servers for other business tools.
Frequently Asked Questions
Is there an official WordPress MCP server?
Yes, two. WordPress.com has a built-in MCP server, and the WordPress project publishes an official MCP Adapter package for self-hosted sites.
Can I make the connection read-only?
On WordPress.com, yes: choose Read only at the sign-in screen. For the MCP Adapter, access depends on which abilities a developer registers and their permission checks.
Do I need an application password?
Not for the WordPress.com server, which uses OAuth. Application passwords come up with tools that connect through the WordPress REST API. If you create one, use a low-privilege user.
Does my site need a particular WordPress version?
The Abilities API, which the MCP Adapter builds on, is available on WordPress 6.9 and above, according to its handbook page.
Can the AI delete my site?
That depends on what you allow. With read-only access or a low-privilege user, far less. Keep backups either way.
Will my content be used to train AI?
WordPress.com’s documentation says data from MCP tools is used only once as part of the original request and not to train AI models. That is a WordPress.com statement about its server. Your AI provider’s own terms apply separately.
Sources
- WordPress.com Developer Resources, WordPress.com MCP Server
- WordPress, MCP Adapter README
- WordPress Developer Resources, Abilities API
- WordPress Core, Application Passwords: Integration Guide
- Model Context Protocol, Specification, version 2026-07-28
All retrieved 6 November 2026.