WordPress.com expanded its Model Context Protocol integration this week, moving beyond read-only access to give AI agents like Claude, ChatGPT, and Cursor the ability to actively create and manage content on connected sites.
The update adds 19 new writing capabilities across six content types, covering posts, pages, comments, categories, tags, and media. Users who connected their AI tools when WordPress.com first introduced MCP support last October could already ask questions about site content and pull analytics data. Now, those same tools can draft and publish posts, build new pages, approve or reply to comments, restructure content categories, and update media metadata including alt text and captions, all through natural conversation without opening the WordPress dashboard.
The practical scope of what this enables is fairly broad. A site owner can instruct an AI agent to publish a post as a draft, assign it to a specific category, add relevant tags, and generate a meta description in a single request. They can ask the agent to create a new category structure for a recipe section, set up an About page with defined sections, or find and fix images across the media library that lack alt text. The agent works through each step, confirms the plan before executing, and flags anything that requires additional input.
Design awareness adds another layer to the content creation side. Before building a page or post, the AI agent reads the site’s active theme to understand its block patterns, color settings, fonts, and spacing, which means generated content fits the existing visual structure rather than arriving as something that needs heavy manual reformatting afterward.
WordPress.com built several safeguards into the system to address the obvious concern around giving an external tool modification rights over a live website. The platform defaults all new posts to draft status. It sends deletions to trash with a 30-day recovery window where possible.
Every action requires the user to confirm before the agent executes anything. The system also respects existing WordPress user role permissions, so an Editor cannot perform actions that administrators reserve for themselves, and a Contributor cannot publish content that requires higher access levels.
Each individual capability carries its own toggle inside the MCP settings dashboard, letting users enable only the operations they actually want available on each connected site.
Existing MCP users need no new installation to access the update.
