Asking ChatGPT for a pre_get_posts filter was the easy part. The harder problem is that our tools need to know something about the environment they are changing. Debugging a race condition in a WooCommerce checkout with an LLM that cannot see your active plugins is mostly pasting snippets into a chat window and hoping. That is why AI in WooCommerce workflows keeps circling back to the Model Context Protocol (MCP).
Why context is the bottleneck
In 14 years of WordPress work, writing the code has never been the slow part. Discovery is. Working out how a legacy plugin hooks into order meta, or why one transient refuses to clear, means reading through files until it clicks. A standard AI assistant cannot see your local database or your file structure at all, so you feed it snippets by hand, which is both error prone and a security risk.
The Model Context Protocol (MCP) is a standard way to close that gap. Run an MCP server and your AI tools can securely query your store’s data, your file structure and even your WP-CLI commands. I wrote about the early version of this in WooCommerce AI and MCP Beta.
Join us for April office hours
Bring your war stories. Maybe you are using AI to refactor legacy code, or you have built a custom MCP server to manage inventory data, or you are simply tired of AI inventing hooks that do not exist in current WooCommerce core. All of it is useful to hear, and it feeds into what gets built next.
15
April
April 15, 2026
16:00 to 17:00 UTC (9:00 PDT / 12:00 EDT)
Join the meeting on Slack
The developer view
Architecturally, AI in WooCommerce workflows is about cutting the time to the first real fix. When your IDE can see through MCP that one wp_options row is autoloading 2MB of data, it names the option instead of offering a generic suggestion. That is the difference between guessing at a refactor and shipping one that holds.
If wiring AI into your WooCommerce workflow is eating the dev hours you meant to spend building, hand it over to me. I have been working on WordPress since the 4.x days.
Before April 15
Automating support replies or generating code, either way the useful part is context. The office hours run on April 15. There will be a recording, but the people who show up live are the ones who get to steer the discussion. Bring your wins, your pain points and your ugliest workarounds.
