AI Assistants (MCP)
Let an MCP-capable AI assistant like Claude Desktop or Cursor discover and run this plugin's content generators directly, with your approval before anything is written.
AI Product Tools registers a small, fixed set of its generation actions with WordPress's own Abilities API. Once your site exposes that through an MCP adapter, an MCP-capable AI assistant (for example Claude Desktop or Cursor) can discover these actions as tools, generate content, and, for a full content-structure run, preview it in plain language before you confirm anything is actually written.
No admin screen for this
This integration has no settings page or dashboard of its own; it is a background capability your WordPress install exposes once the requirements below are met. There is nothing to screenshot here, only what connecting an assistant lets it do.
Requirements
- WordPress 6.9 or later, for the Abilities API (
wp_register_ability()) to exist at all. The plugin checks for this function itself and silently skips registering anything on an older WordPress. - An MCP adapter that turns registered abilities into MCP tools for a client to call. WordPress 7.0 introduced Abilities API support for this as a core-adjacent capability.
- An AI provider connected in Settings, the same BYOK connection every other generator uses. Abilities call out to whichever provider your site is already configured with.
- The user account the assistant authenticates as needs the
manage_woocommercecapability; every single ability checks this, with no plan requirement on top of it.
What an assistant can do
Every ability only generates or previews; none of them write to a product except the one explicit confirm step below.
| Ability | What it does |
|---|---|
| Generate Product Description | Writes an AI description for one product. Generate only; never writes to the product. |
| Generate Product Title | Writes an AI title for one product. Generate only. |
| Generate Product Tags | Writes AI tags for one product. Generate only. |
| Generate SEO Meta | Writes an AI SEO meta title and description for one product. Generate only. |
| Invoke AI Provider | Sends an arbitrary prompt (1 to 8000 characters) straight to your site's configured AI provider. Useful for an assistant that wants to do its own reasoning with your key rather than call a fixed generator. |
| Preview a Content Structure Run | Shows which content structure would write each of up to 100 selected products, the affected count, and any plan limits, without calling AI or writing anything. Returns a short-lived confirm token. |
| Confirm a Content Structure Run | Spends that confirm token exactly once: actually generates and writes content, or queues/links a larger run. The only ability that writes anything. |
Each single-field generator (Description, Title, Tags, SEO Meta) accepts an optional content structure override and otherwise follows the product's normal assignment; none of them work any differently based on plan.
The preview, then confirm flow
This is the one path that actually writes content, and it is deliberately two calls:
Preview
The assistant calls Preview a Content Structure Run with a generator and 1 to 100 product IDs. It gets back the content structure that governs each product, how many products are affected, any plan limits that would apply, a plain-language summary, and a confirm token valid for 15 minutes. Nothing is written yet.
You decide
Because this step is read-only, you can review the assistant's summary (and, in your own chat with it, ask it to explain what it found) before anything touches your catalog.
Confirm
The assistant calls Confirm a Content Structure Run with that same confirm token and the previewed product count. For up to 5 products this runs immediately (synchronously) and writes the result directly. For a larger batch, a Business site gets it queued as an Automation job; a Free or legacy Pro site instead gets a deep link to continue the run manually from the generator page, since direct-apply is capped at 5 products regardless of plan.
A confirm token can only be spent once. A content type still running on legacy custom prompts (Advanced mode, see AI Content Panel) cannot be previewed or confirmed at all; switch it to a content structure first.
How to connect an assistant
- Make sure your site meets the requirements above (WordPress 6.9+, an MCP adapter exposing the Abilities API, a connected AI provider).
- In your MCP client (for example Claude Desktop or Cursor), add your WordPress site as an MCP server, authenticating as a user with
manage_woocommerce. The exact connection step depends on your MCP adapter and client; this plugin only supplies the abilities themselves, not the transport. - Ask the assistant to list its available tools. You should see the 7 abilities above, named with the
ai-product-tools/prefix (for exampleai-product-tools/generate-description). - Try a read-only call first, like Preview a Content Structure Run on one product, to confirm the connection works before asking it to confirm anything.
Limits
| Limit | Value |
|---|---|
| Preview: products per call | 1 to 100 |
| Confirm token validity | 15 minutes, single use |
| Direct-apply (synchronous) cap | 5 products |
| Rate limit, generate/invoke/preview/confirm combined | 700 units per 300 seconds per user by default (your host may adjust this); a synchronous confirm spends 1 unit per product |
| Invoke AI Provider prompt length | 1 to 8000 characters |