If you run WordPress for clients, AI implementation on WordPress stopped being a plugin experiment this year. Between March and September 2026 the platform grew a real stack: a registry of what a site can do, a shared way to talk to model providers, and a protocol so editors like Cursor or Claude can work on a live site with the same permissions as a logged-in admin.

This recap covers AI implementation on WordPress over the last six months, what we actually turn on for projects at 7 Sync Technologies, and what we still keep off production. It is written from client work, not a press-release list.

The three pieces that matter

Most of the noise in 2026 is easier if you treat AI as three layers, not one magic button.

• Abilities API (in core since WordPress 6.9, tighter in 7.0 and 7.1) — plugins and core register named actions with input/output schemas and a permission callback. An agent can ask “what can this site do?” and get a catalogue instead of guessing REST routes.
• WP AI Client / PHP AI Client (in core with WordPress 7.0) — one prompt API and one connector screen, so every plugin does not ship its own OpenAI or Anthropic settings page.
• MCP Adapter — turns those abilities into Model Context Protocol tools. Cursor, Claude, VS Code, and similar clients can discover and run them. You still authenticate with WordPress Application Passwords (or OAuth). If Application Passwords are disabled (Wordfence often does this), the connection fails until you re-enable them.

WordPress 7.0 did not ship a boxed chatbot. It shipped connectors. You still install a provider plugin and add an API key. WordPress 7.1, which this site is on, refined how abilities are exposed (including a clearer public flag) and how input is normalized before an ability runs.

Developer notes worth bookmarking: the official post on the WordPress MCP Adapter, Kinsta’s Abilities API walkthrough, and the Make WordPress AI release posts.

Canonical AI plugin: from images to editor workflows

Core is the plumbing. Day-to-day editor features still live in the canonical WordPress AI plugin. The last six months moved a lot of experiments into something you can actually put on a staging site.

• April 2026 (AI 0.8) — image generation and editing left experiment status and became a feature. Dashboard widgets started showing which abilities and connectors were actually configured.
• July 2026 (AI 1.2) — Suggest Reply for comments, bulk content summaries, and a read-only core/read-content ability so agents can pull posts by ID, slug, or query without a custom endpoint.
• August 2026 (AI 1.3) — in-editor translation for headings and paragraphs, slug suggestions in the permalink UI, better category/tag classification, settings import/export between staging and production, and a Site Health section for the plugin. Custom abilities such as core/read-users and core/read-content are no longer exposed automatically. You opt in under Settings → AI → Admin Experiments. That is the right default.

1.3.0 was tested against WordPress 7.1. If you already connected an agent to those abilities, turn Custom Abilities on after the upgrade or the agent will look blind. Also update any code that still reads the old ai_generated meta keys; they are now prefixed with wpai_.

What we actually implement on client sites

Here is the path we use when a client asks for AI on WordPress without handing the whole admin to a model.

1. Take a backup (UpdraftPlus or host snapshot) and work on staging first.
2. Update WordPress to 7.1.x. Confirm PHP 8.1+.
3. Install only the AI pieces you will use: the canonical AI plugin, one provider connector, and MCP or a hosted MCP bridge if editors will work from Cursor or Claude.
4. Re-enable Application Passwords if Wordfence or another security plugin turned them off. Check Users → Profile. No Application Passwords section means the authorize link will never appear.
5. Connect the agent as a dedicated administrator or editor, not a shared personal login. Approve the application password in wp-admin. Then verify with a read-only site summary before any write.
6. Leave Custom Abilities off until you have a reason. Read content and drafts are enough for most blog work. Publishing, user reads, and settings should stay human-approved.
7. Keep generated posts in draft. A human checks tone, links, and facts before publish. That matches how we ship other content work.

If you still maintain theme PHP, our notes on useful WordPress functions still apply. An ability is a wrapper around the same capability checks you already know. More WordPress tutorials live in the WordPress category.

Builders did not wait for core

Page builders shipped their own agents in the same window. Elementor’s Angie Code can generate widgets and Atomic layouts in a sandbox. We covered that separately in What’s New in Elementor in 2026. Treat builder AI and core AI as two tools: one for layout, one for site operations and content. Do not run both against production on day one.

How we use this at 7 Sync Technologies

At 7 Sync Technologies in Rajkot we use AI on WordPress for drafts, spam triage, plugin inventories, and cautious core updates. We do not let an agent publish, delete users, or dump application passwords into chat. The last six months made that split easier: abilities plus MCP mean the model can do real work, and WordPress still owns permissions.

If you want this stack on a client site, or a staging review before you expose abilities, use the contact page.

Quick checklist

1. WordPress 7.1.x on staging, with a backup
2. One AI provider connector, not three overlapping chat plugins
3. Application Passwords on, Wordfence brute-force toggle confirmed
4. Custom Abilities off until a named integration needs them
5. Agent connection verified with a read-only site_info (or equivalent) before writes
6. Draft-first for generated posts; human publish
7. Watch comment spam and REST abuse after you open MCP

That is AI implementation on WordPress heading into late 2026: not a single plugin, but Abilities, a shared AI client, MCP for agents, and an official editor plugin that finally does translation, slugs, and summaries in the place your editors already work.

Featured photo: Christopher Gower on Unsplash.