--- title: "WordPress AI Plugin 1.5.0: Six New Experiments" url: https://nexterwp.com/blog/wordpress-ai-plugin-1-5-0/ date: 2026-11-05 modified: 2026-11-05 lang: en author: "Aditya Sharma" description: "AI plugin 1.5.0 adds text to speech, MCP Access, WebMCP and three more experiments, and removes three old Abilities names. Here is what changes." image: https://nexterwp.com/wp-content/uploads/2026/11/wordpress-ai-plugin-1-5-0-1024x538.webp word_count: 706 --- # WordPress AI Plugin 1.5.0: Six New Experiments ## Key Takeaways - AI 1.5.0, released on October 29, 2026, adds six new experiments, including Text to Speech, Content Verification, MCP Access and WebMCP for the block editor. - MCP Access installs and activates the MCP Adapter when permissions allow, then adds a Tools → MCP Access screen to show registered Abilities and let site owners expose or hide individual Abilities. - WebMCP lets compatible AI browsers work inside the block editor through the experimental document.modelContext interface, so an agent can read and update the post, insert and edit blocks, save and publish. - Three deprecated Abilities names are removed in WordPress AI plugin 1.5.0: core/read-content becomes core/content-query, core/read-users becomes core/users-query, and core/read-settings becomes core/settings-get. AI 1.5.0, released on October 29, 2026, is the biggest update yet to the official WordPress AI plugin. It adds six new experiments, including text to speech, MCP access and a WebMCP interface for the block editor, and it removes three older Abilities names that some integrations may still call. This guide walks through what is new, what breaks, and what to check before updating. All details come from the official [What’s new in AI 1.5.0](https://make.wordpress.org/ai/2026/11/02/whats-new-in-ai-1-5-0/) post. The plugin listing shows version 1.5.0 and more than 60,000 active installations. Table of Contents ## The Six New Experiments | Experiment | What it does | | ---------- | ------------ | | Text to Speech | Generates an audio version of a post through a configured AI provider that supports speech. Processing runs in the background, the file is saved to the Media Library, and an audio player can be shown on the published post | | Content Verification | Detects C2PA Content Credentials in uploaded JPEG, PNG and WebP images and keeps the manifest with the attachment. It is read-only and does not yet verify signatures cryptographically | | MCP Access | Installs and activates the MCP Adapter when permissions allow, and adds a Tools → MCP Access screen to see registered Abilities and choose which ones agents can use | | WebMCP | Lets compatible AI browsers work in the block editor through the experimental `document.modelContext` interface: read and update the post, insert and edit blocks, save and publish | | Revision Change Summary | Writes a plain-language summary of the differences between two revisions. It is read-only | | Block Container Label Generation | Suggests names for Group, Columns and other container blocks so List View is easier to read | ## MCP Access And WebMCP The two agent-related experiments work at different levels. MCP Access exposes server-side Abilities to outside agents. The screen shows the site’s MCP endpoint and lets you expose or hide individual Abilities, with a way to restore the defaults. WebMCP works inside the browser, so an agent can edit the document through the editor’s existing data stores and changes appear as they happen. Giving an agent access to a live site is a security decision. Our guide to [MCP security for WordPress](https://nexterwp.com/blog/mcp-security-wordpress/) lists what to weigh first. ## Breaking Changes To Abilities Three general-purpose Abilities were synchronised with the versions coming in WordPress core with 7.2. The request and response structures changed, with new `where`, `fields` and pagination inputs for content and user queries. The deprecated aliases from earlier releases are now removed: | Removed name | Use instead | | ------------ | ----------- | | `core/read-content` | `core/content-query` | | `core/read-users` | `core/users-query` | | `core/read-settings` | `core/settings-get` | If an agent, script or plugin calls the old names, update it before upgrading. The post also notes changes to date fields and user lookup behaviour that may need adjustments. ***Also Read:** [WordPress Abilities API](https://nexterwp.com/blog/wordpress-abilities-api/) for how Abilities are registered and called.* ## Other Changes - **Embeddings.** A background sync keeps embeddings for posts and taxonomy terms up to date using WordPress Cron. It is developer infrastructure, and it only runs when a feature registers a need for it. - **Content Translation.** Translation now covers more blocks with rich text and protects blocks that were edited or removed while a request was running. - **Markdown Feeds.** Posts requested with `?output_format=markdown` include approved comments. The old `//feed/markdown/` URLs are no longer supported. - **Settings and connectors.** Features and experiments are separated more clearly, with details on when each runs and what it sends to the provider. Mistral and Vercel AI Gateway join Anthropic, Google and OpenAI on the Connectors screen. - **Abilities Explorer.** Rebuilt with DataViews, with three new REST endpoints for retrieving and running Abilities. - **Smaller fixes.** A Generate title button in the Rename modal, log deletion by age, and protected post titles and excerpts no longer sent to providers. ## Before You Update - **Search your code** for the three removed Abilities names. - **Check Markdown consumers** that use the old feed URL format. - **Review automatic experiments.** Use the new information controls to see which ones send data to your provider. - **Test on staging first,** since several experiments change what editors and agents can do. ## What This Doesn’t Cover This guide did not test the plugin, so it makes no claims about speed, cost or output quality. It does not rank the AI plugin against other options. For a wider comparison and the bigger picture, read the guides below. #### Suggested Reading - [WordPress MCP Server](https://nexterwp.com/blog/wordpress-mcp-server/) - [Best Artificial Intelligence WordPress Plugins](https://nexterwp.com/blog/best-artificial-intelligence-wordpress-plugins/) - [WordPress For The Agentic Web](https://nexterwp.com/blog/wordpress-agentic-web-plan/) #### Stay updated with Helpful WordPress Tips, Insider Insights, and Exclusive Updates – Subscribe now to keep up with Everything Happening on WordPress! Subscribe ## Frequently Asked Questions **Q: Is the WordPress AI plugin 1.5.0 a good update to install right away?** A: AI 1.5.0 is the biggest update yet to the official WordPress AI plugin, but it also changes behavior in ways that can break older integrations. The main risk is the removal of three Abilities names, plus changes to request and response structures for content and user queries. If your site uses agents, scripts, or plugins that call those old names, test on staging first so you catch breakage before it reaches editors or published content. **Q: What breaks when updating WordPress AI plugin 1.5.0?** A: The biggest breakage is around Abilities names. core/read-content, core/read-users, and core/read-settings were removed and replaced with core/content-query, core/users-query, and core/settings-get. The post also says date fields and user lookup behavior changed, so anything that parses those responses may need updates too. That matters most for custom agents and automation, not casual users. **Q: How do MCP Access and WebMCP differ in WordPress AI plugin 1.5.0?** A: They solve different problems at different layers. MCP Access exposes server-side Abilities to outside agents and lets you show or hide individual Abilities from a Tools → MCP Access screen. WebMCP works inside the browser through the experimental document.modelContext interface, so a compatible AI browser can read, update, insert blocks, edit blocks, save, and publish directly in the block editor. One is about server exposure, the other is about in-editor control. **Q: Can an AI browser edit WordPress posts directly with WebMCP?** A: WebMCP is built for that exact workflow inside the block editor. It uses the experimental document.modelContext interface so a compatible AI browser can read and update the post, insert and edit blocks, then save or publish changes as they happen through the editor’s existing data stores. That makes it different from server-side automation because edits are happening in the live editing session rather than through a separate API-style handoff. **Q: What should I check before updating to WordPress AI plugin 1.5.0?** A: The safest pre-update check is your own integration surface. Search code for the three removed Ability names first, then check any Markdown consumers that still use the old //feed/markdown/ URL format because that path is no longer supported. Also review automatic experiments with the new information controls so you know which ones send data to your provider. Nexter WP’s guidance here is basically: stage it before you trust it. **Q: Does WordPress AI plugin 1.5.0 work well as a WordPress AI website builder review topic?** A: This release looks more like infrastructure for an AI-powered site workflow than a finished website builder feature set. The page focuses on text to speech, Content Verification, MCP Access, WebMCP, revision summaries, and block label generation rather than design output or speed claims. It also says it does not test speed, cost, or output quality and does not rank the plugin against other options, so any review should stay grounded in those limits.