Skip to content
AI-Assisted Content5 min read

WordPress Goes All-In on AI: Free Plan MCP Access Is Live and Version 7.3 Targets Native Agent Support

On October 31, WordPress.com dropped a changelog most content teams will want to read twice. MCP — the Model Context Protocol connection that lets ChatGPT, Claude, and other AI agents actually operate your site — is now available to free plan users through November. It was previously behind a paid plan wall since March 2026.

On the same day, AI-powered WooCommerce store building landed for paid accounts. And three days earlier, on October 28, WordPress 7.1.4 shipped with 13 security patches and auto-applied to every WordPress.com hosted site.

That is a dense week for a platform that powers more than 39% of the web.

What the Free MCP Access Actually Gives a Content Team

The WordPress.com MCP server exposes 60+ tools covering posts, pages, plugins, themes, users, site settings, media, comments, and taxonomies. Every tool maps to the WordPress REST API with plain-language descriptions so an AI agent understands each capability without custom configuration.

Connecting Claude or ChatGPT takes a few clicks through the official connectors. Authentication runs over OAuth 2.1, meaning your WordPress.com credentials never touch the AI client. From there, prompts like "create a draft post in the News category with this content" or "list my installed plugins and flag any with available updates" execute directly against the site.

The toggle between read-only and full write access lives in your AI and MCP settings. Individual tools can be switched on or off per site. Content teams wary of unchecked AI edits can enable write access for posts and tags only, leaving plugin management and theme settings strictly off-limits.

WordPress.com describes itself as the only managed WordPress platform with a production-ready, native MCP endpoint requiring no additional plugins or self-hosting configuration.

AI Store Building Is a New Thing Now

Tell the WordPress Agent "I want to sell something" and it installs WooCommerce, designs a store layout, and populates example products as a starting point. Commerce plan accounts get gift cards, product bundles, and shipment tracking on top. The workflow that previously required hours of configuration starts with one sentence.

Store building requires a paid plan. The free MCP access through November lets any site owner test the conversational interface — drafting posts, checking site stats, reorganizing categories and tags — before deciding whether to upgrade.

The WordPress 7.3 Roadmap Content Teams Should Know

The October 29 AI Team office hours focused on finalizing core abilities ahead of WordPress 7.2 Beta 1. But the announcement with longer-term stakes came from AI Team rep Jason Adams earlier in the week: he received approval from WordPress co-founder Matt Mullenweg to build MCP into WordPress core, with version 7.3 floated as the target release.

Mullenweg's stated condition was direct: "throw everything we've got at this to avoid new vulnerabilities."

Adams split the path forward into four areas — MCP, Abilities, OAuth authentication, and end-to-end user experience. The MCP Adapter plugin, which landed on WordPress.org in early October 2026, already passed 60,000 active installs. The plan calls for rapid iteration on the adapter during the 7.2 release cycle, then a formal proposal to bring MCP into core for 7.3, either merged outright or bundled so it can continue evolving on its own schedule.

The current adapter supports both the 2025-11-25 and 2026-07-28 MCP specifications. WordPress 7.2 Beta 1 landed October 20, with RC1 scheduled for November 17 and the final release on December 8.

What This Means for Content Operations Day-to-Day

The workflow gap this closes is not writing. It is the mechanical work around writing. Setting categories, writing meta descriptions, updating alt text on a media library batch, scheduling drafts, building taxonomy structures for a content rebrand — all of that can move to a conversation with the AI. The human sets the direction and approves the result. The AI handles the repetitive clicks.

For content teams running authority news sections that publish industry updates on a schedule, the practical upside is concrete. An AI agent can draft a post, apply the correct category and tags, write an excerpt and meta description under 160 characters, and save everything as a pending draft. A human editor reviews it and publishes. The editorial judgment stays human. The production overhead does not.

Self-hosted sites are not left out. Sites running Jetpack can use the same WordPress.com MCP server at no additional Jetpack plan cost. Sites running WordPress 6.9 or newer can install the official MCP Adapter (version 0.7.1) from the WordPress.org directory. The recommended setup is a dedicated application password scoped to a contributor-level account rather than a site admin, tested against a staging copy before production.

Three Steps to Take This Week

If your site is on WordPress.com, free or paid, open Preferences, then AI and MCP, and enable access. Connect Claude via the official Claude Connector or ChatGPT through the plugin directory. Run read-only first — ask the agent to list your draft posts and your most recently published content, then verify the output matches your dashboard before enabling any write tools.

If you are on self-hosted WordPress running 6.9 or newer, install the MCP Adapter from the plugin directory. Create a contributor-level application password, configure the adapter against your staging environment, and test task completion before pointing it at a live site.

WordPress 7.3 is still a release cycle away. The MCP Adapter, the free WordPress.com access, and the 60-plus tool surface available today are already enough to materially change how a content team moves from brief to published draft.

Sources: