Writing with AI is already part of everyday work for many website owners. Getting that work into WordPress often still involves copying text, finding the right page, adjusting metadata and clicking through the editor. Your.Online’s AI Connector, developed by Progress Planner, brings those steps closer to the conversation.

The WordPress plugin connects a compatible AI tool to a website through the Model Context Protocol, or MCP. Its purpose is practical: let an assistant work with site content and perform supported actions using the permissions of the connected WordPress account.

This article looks at the test version installed on Newfun.nl in October 2026. It is an early look at the connector’s capabilities, rather than a claim that every feature is generally available across Your.Online’s hosting brands.

From a writing assistant to a website workflow

The connector’s settings describe support for creating posts and pages, refining existing content and publishing when requested. It also offers work on image descriptions, featured images, categories and tags. Site information can give the assistant useful context before it starts writing.

That opens up a more connected editorial process. A website owner could ask an assistant to find relevant existing articles, prepare a follow-up post and save it as a draft for review. Another request might focus on improving image descriptions or organizing content. These are example workflows: the actions available depend on account permissions, active plugins, site settings and the capabilities of the AI client.

The plugin also identifies WooCommerce and Yoast SEO as sources of additional context when they are active. This makes the website’s own setup part of the interaction, instead of requiring the owner to explain everything from scratch.

Connecting through OAuth

In our initial setup on Newfun.nl, Codex registered the website’s MCP endpoint and completed an OAuth sign-in through WordPress. The connector then showed Codex in its list of connected AI tools. That confirmed the account connection; it did not by itself demonstrate every content-management action.

Our first publication used the WordPress editor because the running AI session had not loaded the connector’s tools. We subsequently connected through an authenticated MCP client, read this article through the AI Connector and used its update-post tool to submit this revised version to the live site. This tests an update to an existing published post; it is not a test of creating a new post or changing a draft to published status.

Publishing remains a deliberate choice

The connector works with the permissions of the connected WordPress account. Its settings include a “Save as drafts only” option for owners who prefer to complete publication themselves. There are also controls to pause AI access and disconnect an individual tool.

These controls matter in day-to-day use. A request to inspect content is different from a request to change it, and preparing a draft is different from making it public. Clear instructions help keep those steps separate: “Review these posts without changing anything” and “Save this as a draft” describe different outcomes.

The test version adds site guidance

The build being tested also introduces guidance for editing, publishing, design and recommendations. The accompanying development notes describe a bundled audit workflow and suggestions for recurring maintenance, including draft reviews, content and internal-link reviews, and indexability checks.

That is a promising direction, but a suggestion is not a scheduled task. The AI client still decides whether to consult the guidance and must support scheduling for unattended checks. The plugin does not add its own server-side scheduler.

Why this fits Your.Online’s direction

Your.Online announced its acquisition of Progress Planner in June 2026, with the team joining to lead AI development across the group. Progress Planner’s own announcement emphasized helping website owners keep their sites relevant and improving over time.

The AI Connector gives that ambition a concrete application: bringing the conversation closer to the website where work needs to happen. Its value will depend on how reliably it handles real editorial tasks, respects permissions and reports what actually changed. This early version provides a useful starting point for testing exactly that.