Skip to content
weLabsweLabsStorefront Playbook
Live demoQuickstart

Features

AI and automation

Let Claude or another MCP client read and update your storefront's content, look and SEO in plain language, through permission-checked WordPress abilities.

New

Ask an AI assistant to “change the promo popup headline” or “find products missing a meta description and write one for each”, and it’s done, saved exactly as if someone had made the change in wp-admin. The Companion plugin publishes the storefront’s settings and each item’s SEO as abilities: named, schema-checked actions that Claude or any other MCP client can discover and run, within the permissions of the WordPress user it acts as.

Where it shows
Your AI assistant (Claude or another MCP client), connected to WordPress
Configure in
An MCP adapter in WordPress and an Application Password for the user the assistant acts as
Requires
WordPress 6.9 or later, HTTPS and pretty permalinks
Try it in Demo Mode
Not available: Demo Mode has no WordPress to connect to
  • Refresh a campaign: update the hero slider, promo cards, sale banner, CTA banner or Today’s Deals copy.
  • Edit pages: add FAQ questions, update contact details and opening hours, or choose which page serves each policy.
  • Adjust the look: switch the colour palette, reorder the mobile tab bar, rework footer columns.
  • Fix SEO at scale: find products, categories, tags, brands, posts or pages missing a title, description or sharing image, then fill them in. Hide an item from search, or change the website name and SEO patterns.
  • Audit: ask what any setting currently is, before deciding what to change.

Storefront settings. Twenty-one sections, each with a read and an update ability:

Area Sections
Look General (social links), Colors, Footer, Mobile tab bar
Home and shop Home slider, Shop slider, Promo tiles, Promo popup, Sale banner, Deals, CTA banner, Testimonials
Pages FAQ, Contact page, Policy pages
Product page Product page, Trust badges, Wishlist, Compare, Back-in-stock notifications
Search SEO (website name, default image, patterns and page settings per language)

A map ability lists every section and what it controls, so an assistant can find its way without being told. Updates are partial: fields you name are merged, and a list is replaced as a whole.

Per-item SEO. Three abilities find items and their SEO gaps, read an item’s SEO, and update it, for products, posts, pages, product categories, tags and brands. Updates write to the source in charge: Yoast SEO or Rank Math if one is active, otherwise the Companion plugin’s own SEO fields. The read shows what the storefront will actually print and where each value came from.

Some settings are deliberately not offered to an assistant, not even to read:

  • sign-in credentials and Turnstile keys;
  • API access rules and customer sessions;
  • payment security settings;
  • header and footer custom scripts;
  • the newsletter provider;
  • the header builder.

These can only be changed by a person in wp-admin. Payment keys are never exposed either: they live in the payment plugins’ own settings.

  1. WordPress checks permission. Storefront settings require the same administrator permission as the settings screen. Per-item SEO follows WordPress’s own editing rights, so an assistant acting as a Shop Manager can edit product SEO, and one acting as an Editor can edit posts and pages.
  2. Your assistant asks before it writes. Read abilities are marked read-only; MCP clients ask you to approve any tool that changes something.
  3. Every update is validated. Input is checked against the ability’s schema, and every image must be a real Media Library image. If anything fails, nothing is saved.
  4. It saves the same way wp-admin does, through the same cleaning and cache clearing, so the change reaches Shoppers like any other: within about five minutes.

Turn on an MCP adapter in WordPress (WooCommerce’s built-in MCP feature, or the standalone MCP Adapter plugin), create an Application Password for the user the assistant will act as, and point your MCP client at your store’s MCP address over HTTPS. The step-by-step guide is in AI agents.

  • WordPress 6.9 or later. On older versions the abilities aren’t registered and nothing else changes.
  • WooCommerce’s MCP feature is experimental and needs permalinks other than Plain.
  • WooCommerce’s own abilities, such as product queries, appear alongside the Companion plugin’s.
  • The Payment & Security card has no ability yet; edit it in wp-admin.
  • Scripts and other tools can call the abilities too, over the WordPress REST API with an Application Password. See REST API.
Storefront Playbook · Built by weLabsFeaturesFAQTalk to us