Kief Studio

WordPress AI Agents Can Now Publish to Your Site. Who Controls It?

Build

  • Published
  • Updated
  • 8 min read
Parallel gold and violet light lines, one bending upward at right, cover for a note on AI agents publishing to WordPress

TL;DR: Since March 2026, WordPress AI agents on WordPress.com can draft, edit and publish through an MCP server, with confirmation at each step. Self-hosted WordPress 7.0 added an AI Client and Abilities API, and an official MCP Adapter plugin exists. Give agents the smallest role that works, keep approvals on, and review their access often.

WordPress AI agents got real write access in 2026. On March 20, WordPress.com announced that tools like Claude, ChatGPT and Cursor can now draft posts, edit pages and manage content on WordPress.com sites through conversation. Two months later, WordPress 7.0 brought an AI Client into core for self-hosted sites.

The headline was about convenience. The question I care about is the one underneath: when software can publish to your site, who decides what goes live, and how do you take that access back? That is a website ownership question as much as an AI one.

Update, October 2026: we first published this note in March 2026. WordPress 7.0 has since shipped, so we have replaced our predictions with what it actually includes, refreshed the usage figures, and removed statistics we could not trace to a primary source.

What did WordPress.com launch for AI agents?

WordPress.com first opened its MCP server in October 2025, "giving AI agents like Claude, ChatGPT, and Cursor their first window into WordPress.com site content, analytics, and settings." That version let agents read. The March 2026 update let them act: "drafting posts, editing pages, and managing content on behalf of users, all with explicit user confirmation at every step." (WordPress.com, via PR Newswire (opens in a new tab))

MCP, the Model Context Protocol, is the open standard that lets an AI tool call another system's functions. WordPress.com says its server is "secured with OAuth 2.1" and works on "all paid WordPress.com plans." (WordPress.com, via PR Newswire (opens in a new tab)) The MCP specification itself describes a protected server as an "OAuth 2.1 resource server" that accepts access tokens issued on behalf of a resource owner. (Model Context Protocol specification (opens in a new tab))

The safeguards WordPress.com built in

Credit where it is due. WordPress.com says "Updates require explicit user confirmation before any action is taken," that "changes to already-published content are clearly flagged as going live immediately," and that "The MCP server is opt-in only, with nothing enabled by default. Users can choose which capabilities are active, site by site." (WordPress.com, via PR Newswire (opens in a new tab)) Those are sensible defaults for WordPress AI agents. The risk sits with the person who turns them off to save a click.

Do WordPress AI agents work on self-hosted sites?

Yes, by a different route. The WordPress.com launch applies to sites hosted on WordPress.com. Self-hosted WordPress got its own building blocks.

WordPress 7.0, released May 20, 2026, added "A new AI Client in Core" that "lets WordPress communicate with generative AI models," with connections "managed from a single hub in the dashboard." The release notes add that "The AI Client combined with the Abilities API" brings "workflow automation, and creation tools to your website." (WordPress.org News (opens in a new tab))

The release post does not mention MCP. That piece lives in a separate package: the MCP Adapter, which WordPress describes as "The official WordPress package for MCP integration that exposes WordPress abilities as Model Context Protocol (MCP) tools, resources, and prompts for AI agents." (WordPress MCP Adapter on GitHub (opens in a new tab)) So self-hosted WordPress AI agents need a plugin or adapter that someone installs and configures. That someone should be you or a person you trust.

Why the scale matters

As of October 31, 2026, W3Techs reports that "WordPress is used by 58.2% of all the websites whose content management system we know," which is 39.5% of all websites, and that version 7 already runs on 67.7% of WordPress sites. (W3Techs (opens in a new tab)) Our March note quoted older figures. The point stands: a change in how WordPress handles AI reaches a large share of the web quickly.

Who controls your site when an AI agent can publish?

On WordPress.com, every connection from WordPress AI agents runs through one company's OAuth, API and servers. That can be a reasonable trade. It is also a dependency: the platform decides which capabilities exist, how confirmation works and what happens to access when plans change.

The WordPress community has argued about central control for a while. In June 2025 the Linux Foundation announced the FAIR Package Manager project, describing it as "a federated and independent repository" for plugins and themes, and saying "Vendor-neutral package management for content management systems like WordPress provides critical universal infrastructure." (Linux Foundation (opens in a new tab)) We covered the governance side in who actually controls WordPress, so I will not repeat it here.

For a business owner, the practical version is simpler. Write down who holds the keys today. Our knowledge base has a short guide on who owns the website and the login, and I have written about who owns the site, the host and the login (opens in a new tab). If an agent can publish, it belongs on that list.

Glowing fiber optic patch cables plugged into a rack panel, like the many connections AI agents can hold into one website
Every connection WordPress AI agents hold into your site is an identity with access, and each one needs an owner.

What can go wrong with WordPress AI agents?

The risk is not hypothetical. In November 2025, the National Vulnerability Database published CVE-2025-11749 for a popular AI plugin. NVD's description says the AI Engine plugin "is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.3 via the /mcp/v1/ REST API endpoint that exposes the 'Bearer Token' value when 'No-Auth URL' is enabled," making it possible for unauthenticated attackers to extract the token and perform actions "like creating a new administrator account." NVD lists its CVSS score as 9.8, critical. (NIST National Vulnerability Database (opens in a new tab)) The plugin's WordPress.org page lists more than 90,000 active installations today. (WordPress.org Plugin Directory (opens in a new tab))

That was one plugin and one setting. The broader pattern has a name. The OWASP Gen AI Security Project lists "Excessive Agency" in its LLM Top 10 and says its root cause is "typically one or more of: excessive functionality; excessive permissions; excessive autonomy." Its first fix is to "Limit the extensions that LLM agents are allowed to call to only the minimum necessary." (OWASP Gen AI Security Project (opens in a new tab))

Agents are accounts too

Each of your connected WordPress AI agents is a non-human identity with standing access. Most small businesses know roughly who has admin rights on their site. Far fewer could list which WordPress AI agents can write, which tool each belongs to, or what happens to that access when someone cancels a subscription. Treat agent access the way you would treat a contractor's login, which is the idea behind agentic security.

Stores raise the stakes

W3Techs reports WooCommerce on 19.7% of WordPress sites. (W3Techs (opens in a new tab)) Once WordPress AI agents can touch product listings, a bad edit is not a typo. It is a wrong price at checkout. Keep commerce changes behind the strictest approval you have.

A simple rule works for most shops: agents may suggest product copy and draft listings, but prices, stock levels, shipping rules and checkout settings change only when a named person approves them. Write that rule down before anyone connects a tool, not after the first mistake.

How do you set up WordPress AI agents safely?

Here is the checklist I would use for any site, hosted or self-hosted.

  1. Use the smallest role. WordPress documents a Contributor as "somebody who can write and manage their own posts but cannot publish them," and an Author as "somebody who can publish and manage their own posts." (WordPress.org documentation (opens in a new tab)) For most WordPress AI agents, Contributor is enough: the agent drafts, a person publishes.
  2. One connection per agent. Separate accounts make it obvious which tool did what, and let you revoke one without breaking the rest.
  3. Turn on only the capabilities you need. WordPress.com lets you choose them site by site. On self-hosted sites, expose only the abilities the job requires, as OWASP advises.
  4. Keep confirmations on. OWASP recommends human-in-the-loop control "to require a human to approve high-impact actions before they are taken." Publishing is a high-impact action.
  5. Review access monthly. List every connected agent, who set it up and why. Remove what nobody can explain.
  6. Keep backups and a change log. If an agent publishes something wrong, you want the previous version and a record of what changed.
  7. Patch AI plugins quickly. CVE-2025-11749 affected versions up to 3.1.3, so the fix was an update plus a new token.

If you want a quick outside view of your site's basics, LTFI offers a free website grade (opens in a new tab) covering security, search, DNS, email, speed and privacy basics.

Frequently asked questions

Can AI agents publish to my WordPress site without asking?

On WordPress.com, the company says updates need explicit user confirmation and the MCP server is off until you enable it. On self-hosted sites, it depends on the plugin and the role you grant, so check both.

Does WordPress 7.0 include an MCP server?

The 7.0 release notes describe an AI Client in core and the Abilities API. MCP support for self-hosted sites comes from the separate, official MCP Adapter package.

Which user role should WordPress AI agents get?

Start with Contributor, which can write but not publish. Raise it only when a person has a clear reason, and give each agent its own account.

What was CVE-2025-11749?

A critical flaw in the AI Engine plugin, up to version 3.1.3, that exposed a bearer token through its MCP endpoint when a no-auth setting was on. Updating and replacing the token fixed it.

How do I remove access for WordPress AI agents?

Revoke its connection or application password, delete or downgrade its user account, and rotate any tokens it held. Then check recent changes it made.

Is WordPress.com or self-hosted WordPress safer for AI agents?

Neither is safe by default. WordPress.com ships with confirmations and opt-in controls. Self-hosted sites give you more control and more responsibility for plugins and settings.

Where we fit

Kief Studio runs websites for owners who do not want the site to become a second job. Our managed website operations covers hosting, design, writing, publishing, search and security: we host the site on dedicated machines, publish on a schedule and watch it, so you never log into a server. When a site needs to do more than a template allows, our custom web application work builds it around how you already run the business.

If you are deciding whether WordPress AI agents belong on your site, we can help you decide which roles they get, which actions need a person, and how to take access back. We have kept client relationships for more than 13 years by asking those questions early.

First conversation is free. No commitment.

Tell us how your site is set up today

Related articles

  1. Automate

    AI Agents Now Hit 66% Task Success. The Gap in Yours Is AI Agent Integration

    AI agents hit 66% task success on OSWorld, yet most small businesses see little. What's missing: AI agent integration with least privilege and human approval.

    Amelia Gagne

  2. Automate

    McKinsey Runs 25,000 AI Agents. Your Team of Four Can Run the Same Play.

    McKinsey runs 25,000 AI agents. A small team needs a few, each with one job, wired to its own tools through MCP, with a person checking. How to start.

    Amelia Gagne

  3. Build

    White-Label AI Agents: What an Agency Actually Owns When It Rebrands One

    White-label AI lets an agency rebrand a vendor's agent. Who holds client access under OAuth, what the FTC expects of your claims, and the real math on margins.

    Brian Gagne