The official WordPress.com connector for Claude, built on the Model Context Protocol (MCP) and secured with OAuth 2.1. It grants Claude read-only access to a site's live data so users can ask natural-language questions about real traffic, comments, and content history directly in the Claude interface. Access is scoped, revocable, and listed in Claude's connectors directory.
WordPress.com offers an official, supported connector for Claude that lets you query your site’s real-time data in conversation. It builds on WordPress.com’s existing Model Context Protocol (MCP) infrastructure and OAuth 2.1 support, and it’s listed in Claude’s connectors directory — so setup is a few clicks with clear, revocable permissions rather than a manual integration.

How to connect
- Enable MCP on your WordPress.com account (available on paid plans).
- Choose the tools you want to expose to Claude in the MCP settings.
- Add the connector in Claude’s settings: browse the connectors directory, search “WordPress.com,” and connect.
- Authorize by logging in to WordPress.com and granting read-only access via OAuth 2.1.

The grant is read-only — Claude can see your content but cannot create, update, or delete posts — and you can revoke it at any time from either platform.
What you can ask
Once connected, Claude answers from your site’s live data instead of generic knowledge, which turns routine analytics questions into plain-language queries:
"Show me my site's traffic for the last 30 days.""Summarize recent comments across my site.""Which posts haven't been updated in over a year?""Show me pages with high traffic but low engagement."
These draw on the same data and tools as the WordPress.com dashboard, surfaced through conversation rather than a reporting UI.
Because it’s an officially maintained connector, it should track changes on both platforms over time rather than breaking as either evolves.
- Claude Connector
- WordPress.com
- Model Context Protocol (MCP)
- OAuth 2.1
- AI Integration
- Site Analytics



More Guides
Run disciplined SEO A/B tests in seven steps — one metric, two variations, randomized segments, run to significance, track, analyze the winner, and iterate.
Build a topic cluster in seven steps — select and score a pillar, validate it, map subtopics, align to intent, architect internal links, publish, and measure.
Prepare your site for AI search in five steps — content architecture, entity consistency, E-E-A-T, structured data, and machine-readable structure.
Get your content cited by AI in seven steps — answer capsules, link-free extraction, original data, digital PR, community presence, consistent messaging, and tracking.
A seven-step walkthrough for setting up Google Search Console on a new site — property type, DNS verification, sitemap, GA4 link, users, URL checks, and a monitoring routine.