If you read our previous guide on how to install MCP on a self-hosted WordPress.org site, you’ll know the process involves installing a plugin, generating Application Passwords, installing Node.js, and editing a JSON config file. It’s absolutely doable, but it takes around 15 minutes and requires some technical comfort.
WordPress.com is a completely different story. Thanks to built-in OAuth 2.1 support and a native Claude connector, you can have your WordPress.com site talking to Claude AI in under two minutes — no plugins, no terminals, no config files.
Here’s exactly how to do it, plus a full comparison of both approaches so you can choose the right one for your setup.
How to Connect Claude to WordPress.com (2 Steps)
Step 1: Enable MCP Access on WordPress.com
- Log in to your WordPress.com account.
- Click your profile avatar in the top right corner to open your profile menu.
- In the left sidebar, look for the MCP option.
- Toggle it on to enable AI tool access for your account.
That’s all you need to do on the WordPress.com side. The MCP server is already built in — you’re just switching it on.
Step 2: Connect in Claude.ai
- Open claude.ai in your browser (or the Claude mobile or desktop app).
- Go to Settings → Connectors.
- Search for WordPress.com in the connector directory.
- Click Connect.
- A browser window will open asking you to approve the connection via OAuth — click Approve.
That’s it. Your WordPress.com site is now connected. You can immediately start asking Claude to create posts, check your content, manage categories, and more — all from the chat interface.
💡 Try it: Once connected, ask Claude: “How many posts do I have on my site?” or “Draft a new post about [your topic].”
What Can You Do Once Connected?
Once your WordPress.com site is connected to Claude via MCP, you can manage your entire site through natural language conversation:
- ✅ Create, edit, and publish posts and pages
- ✅ List and search your existing content
- ✅ Manage categories and tags
- ✅ Check site settings and statistics
- ✅ Update post excerpts, slugs, and SEO metadata
- ✅ Manage media and featured images
- ✅ Schedule posts for future publication
WordPress.com vs WordPress.org MCP: Full Comparison
Not sure which setup applies to you, or thinking about switching? Here’s a complete side-by-side breakdown:
| Feature | WordPress.com | WordPress.org (Self-Hosted) |
|---|---|---|
| Works in Claude.ai (browser/app) | ✅ Yes | ❌ Not yet |
| Works in Claude Desktop | ✅ Yes | ✅ Yes |
| Works in Claude Code | ✅ Yes | ✅ Yes |
| Setup time | ~2 minutes | ~15 minutes |
| Technical skill required | None | Moderate |
| Plugin required | None | MCP Adapter plugin |
| Node.js required | No | Yes (v18+) |
| Config file editing | No | Yes (JSON file) |
| Authentication method | OAuth 2.1 (secure, one-click) | Application Password |
| Token management | Automatic | Manual |
| Multi-site support | ✅ Yes | One site per config entry |
| Cost | Free (with WordPress.com plan) | Free (Claude subscription only) |
Which Should You Choose?
Choose WordPress.com MCP if:
- You want the fastest, simplest setup possible
- You primarily use Claude through the browser or mobile app
- You don’t want to manage plugins, config files, or credentials
- You run multiple WordPress.com sites and want them all accessible from one Claude account
Choose WordPress.org (Self-Hosted) MCP if:
- Your site is self-hosted and you can’t move to WordPress.com
- You primarily use Claude Desktop or Claude Code
- You need full control over your server and data
- You want to build custom MCP abilities specific to your site or plugins
The Bottom Line
WordPress.com’s native MCP integration is one of the most seamless AI connections available for any CMS right now. If your site is hosted on WordPress.com, there’s no reason not to turn it on today — it takes two clicks and instantly transforms how you manage your content.
If you’re on a self-hosted WordPress.org site, the setup is a little more involved but absolutely worth it. Check out our step-by-step guide to get it done in 15 minutes:
Leave a Reply