Claude + WordPress: What the Integration Can (and Can't) Do in 2026
Yes — WordPress.com is an official connector in Claude’s directory. Automattic shipped the WordPress.com connector on February 5, 2026, calling it the first of its kind for a WordPress host. But the answer splits in two, and most guides blur it: the WordPress.com connector is read-only, and self-hosted WordPress takes a completely different path (the official MCP Adapter plugin on WP 6.9+). Either way, the limit that applies to every Claude integration applies here: it only works inside a conversation you start. Nothing publishes on a schedule, nothing watches your comment queue, and nothing runs while you’re away.
Here’s exactly what each path does, how to set them up, where the limits bite, and what to use if you want WordPress work that runs on its own.
Path 1: the official WordPress.com connector (read-only)
If your site is hosted on WordPress.com, this is the one-click route. You need a paid WordPress.com plan, then you enable MCP in your WordPress.com account settings and connect via Claude’s Settings → Connectors → WordPress.com with OAuth.
Once connected, Claude can:
- Review traffic and engagement — pull stats and summarize what’s working.
- Summarize comments — see what readers are actually saying across posts.
- Audit content — find stale posts, broken links, and internal-linking opportunities.
- Advise on strategy — build style guides and topic ideas from your existing catalog.
What it will not do: create, update, or delete content. The directory connector is positioned read-only. Under the hood it talks to WordPress.com’s official remote MCP endpoint (https://public-api.wordpress.com/wpcom/v2/mcp/v1, OAuth 2.1 with PKCE), and per WordPress.com’s MCP docs write tools do exist at the endpoint level — they’re just disabled by default and have to be toggled on per-tool in your WordPress.com settings. Out of the box, Claude is an analyst for your site, not an author on it.
Path 2: self-hosted WordPress via the MCP Adapter
Self-hosted sites can’t use the directory connector. The official route is the WordPress MCP Adapter plugin — a canonical WordPress.org project that exposes your site’s “Abilities” over MCP. It requires WordPress 6.9+ (the release that shipped the Abilities API, a machine-readable registry of what your site can do, built specifically for AI agents). It’s a separate plugin, not bundled into core. If you find the older Automattic/wordpress-mcp plugin in a tutorial, skip it — it was archived in January 2026 in favor of the MCP Adapter. For stdio clients like Claude Desktop, Automattic’s mcp-wordpress-remote proxy bridges the connection.
And there’s a third option that predates MCP entirely: the WordPress REST API with Application Passwords (core since WP 5.6). Any tool that can make HTTP calls gets full CRUD on posts, pages, comments, media, and categories at /wp-json/wp/v2/ — create drafts, schedule posts, moderate comments. This is the surface most real WordPress automation runs on, and it’s what matters for the Carly section below.
The limits that actually matter
Claude’s WordPress story is the strongest of any website platform — an official directory connector plus an official self-hosted plugin. But its shape is “an assistant you operate,” not “an agent that runs.” Three limits define it:
- The directory connector can’t write. Ask the WordPress.com connector to publish a post and it can’t — it’s read-only by design. Writes require flipping per-tool toggles at the endpoint level or running the self-hosted MCP Adapter route.
- No triggers, no monitoring. Everything happens inside a conversation you start. There’s no “every Friday, draft the weekly roundup” or “when a comment needs moderation, triage it.” Nothing fires on an event — you have to be there, prompting.
- Laptop-bound for anything scheduled. The closest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on editorial assistant.
So Claude is great for “audit my stale content right now” and not built for “keep my publishing calendar and comment queue moving on their own.”
If you want WordPress work that runs on its own: Carly
The moment you want something to happen on your site without you in the chat — a weekly draft compiled and waiting every Friday, comments triaged every morning, social blurbs generated the moment a post goes live — you’ve crossed past what Claude’s connector is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat. WordPress connects to Carly via your own API key — for self-hosted sites, generate an Application Password and paste it on carlyassistant.com/integrations — and it works like any native connection:
- Every Friday afternoon, Carly compiles the week’s notes and newsletter material into a formatted WordPress draft, ready for your Monday review.
- Every morning at 8, pending comments pulled, summarized, obvious keepers approved, and replies drafted for the real questions.
- When a post publishes, Carly generates the social blurbs and drafts the email announcement from the post content.
- Monthly, a stale-content report: posts untouched for 12+ months that still get traffic, ranked by refresh priority.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it with you.
- Actually sends — drafts and sends email across Gmail and Outlook, updates records, manages tasks.
- Connects to anything — 200+ native integrations, plus any other tool via your own API key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude (WordPress.com connector / MCP Adapter) | Carly | |
|---|---|---|
| Read stats, comments, content | Yes | Yes |
| Create and schedule drafts | No (connector is read-only; writes need self-hosted MCP setup) | Yes (REST API) |
| Acts on triggers / events | No | Yes |
| Publishes weekly drafts on its own | No | Yes |
| Works while laptop is closed | Directory connector yes, but chat-only; local MCP no | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude’s connector is a strong site analyst inside a chat. Carly is a teammate that keeps the blog, comments, and follow-ups moving on their own.
Frequently Asked Questions
Does Claude work with WordPress?
Yes. WordPress.com is an official connector in Claude’s directory (paid WordPress.com plans, OAuth, read-only — stats, comment summaries, content audits). Self-hosted sites use the official WordPress MCP Adapter plugin on WordPress 6.9+ instead. Like every Claude integration, both only work inside a conversation you start.
Can Claude publish posts to WordPress?
Not through the directory connector — it’s read-only. The WordPress.com MCP endpoint does have write tools, but they’re disabled by default and must be toggled on per-tool in your WordPress.com settings. On self-hosted sites, the MCP Adapter exposes whatever Abilities your site registers. Either way Claude only writes when you’re in the chat asking it to.
How do I connect Claude to a self-hosted WordPress site?
Update to WordPress 6.9+, install the official MCP Adapter plugin, and bridge it to Claude Desktop with Automattic’s mcp-wordpress-remote proxy. The older Automattic/wordpress-mcp plugin was archived in January 2026 — use the MCP Adapter.
What if I want my WordPress workflow to run without me in the chat?
That’s outside what Claude’s connector does — it reads and advises inside a conversation. Carly connects to WordPress via your Application Password, fires on events and schedules 24/7 in the cloud, and can compile drafts, triage comments, and send the announcement email. AI agents start at $35/month.
More: Claude + WooCommerce · Claude + Squarespace · Claude + Webflow · Claude + Wix · Claude connectors · Can Claude send emails
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
