Blaze MCP Toolkit for WooCommerce

By Blaze Commerce

0+ active installationsVersion 1.2.0

Ask Claude or ChatGPT how your WooCommerce store is doing: sales, payments, errors, failed jobs, updates and API access. Our tools are read-only.

Description

Blaze MCP Toolkit for WooCommerce connects your WooCommerce store to Claude or ChatGPT so you can ask plain questions and get straight answers: How did we do this week? Why did sales drop on Tuesday? Is anything broken? WooCommerce’s own AI connection can look up products and orders. This plugin adds what it can’t see: sales totals that match your WooCommerce reports, whether each payment method is still taking orders, PHP errors, failed background jobs, recent plugin updates, and who has API access to your store.

It’s read-only by default: out of the box it never changes your store, never sends customer names, emails or addresses from your orders to the AI, and adds nothing to the pages your customers load. It’s a weekly check-up you can run in two minutes, so you spot problems before your customers do.

One thing to know up front: the same connection also carries tools from WooCommerce itself and from the plugin that connects your AI assistant (Enable Abilities for MCP or Easy MCP AI), and some of those can edit orders and products or return customer details. The plugin’s setup screen lists them and shows where to switch them off.

What you can ask

  • “Run my weekly store review.”
  • “Are payments working? Has any payment method gone quiet?”
  • “Sales were down yesterday. Did anything change on the site?”
  • “Are there failed orders I should chase?”
  • “What’s driving refunds this month?”
  • “Is anything broken on the store right now?”
  • “Who has API access to my store?”

Tools this plugin adds

Our store check tools

  • Store health (health-summary): red, amber or green for PHP errors, background jobs and updates, plus your WordPress, WooCommerce and PHP versions. It reads the tail of your PHP and WooCommerce error logs, groups repeated errors, names the plugin or theme they come from, and strips out emails, card numbers, API keys and passwords before anything reaches the AI. If the site has no error log it can read (common on managed hosts), it says so and shows amber rather than a false green. Background jobs covers failed and overdue Action Scheduler jobs from the last 7 days, with order emails, subscription renewals, webhooks and stock syncs called out.
  • Update history (update-history): a dated list of plugin, theme and WordPress updates, installs, activations, deactivations and theme switches, recorded from the day you activate the plugin and kept for 180 days. Changes made outside WordPress, such as a deploy over SSH or git, are not seen.
  • Access check (access-check): WooCommerce REST API keys, webhooks and application passwords, with flags for write keys unused for 90 days and webhooks that send order data. It never returns keys, secrets, full webhook addresses or user names.
  • Payment health (payment-health): for each payment method, red, amber, green or unknown for four questions. Is it still taking checkout orders, judged against its own last 28 days of orders and the store’s busy and quiet hours? Were recent checkouts left unpaid or cancelled unpaid more often than the method’s own earlier orders? That one is only judged where the toolkit knows the payment is taken at checkout: Stripe card; WooCommerce PayPal Payments card and wallets (PayPal, card fields, card button, Google Pay, Apple Pay, Fastlane); WooPayments card and wallets; and Square card and Cash App Pay. Bank transfer, cheque and cash on delivery skip it. Other methods, including PayPal Payments’ redirect and voucher methods and WooPayments’ separate local payment methods, show their unpaid orders as counts without a colour, because some of them settle later, so that question reads unknown. Did the payment plugin fail background jobs (Stripe and WooPayments), log errors or record webhook delivery problems (Stripe only)? Where a check isn’t supported for a plugin it is not run and doesn’t count either way. It looks back over a rolling window you choose (1 to 168 hours, 24 by default), not a past calendar period.
    • It only asks: it never changes orders, settings or payments, never retries anything and never contacts your payment provider. Any fix it suggests is yours to make.
    • Unknown means it could not check, not that all is well. It says which checks it couldn’t run and why, for example too few orders to judge, a payment method whose settlement timing it can’t confirm (its unpaid orders are counted, not judged), a supported payment plugin’s log or job list it couldn’t fully read, or a role that can’t see diagnostics.
    • When WordPress hasn’t loaded the list of payment plugins (mostly in scheduled or command-line runs), payment health can’t give an all-clear: it reads unknown unless it finds a problem, which it still reports, and it may leave out switched-on methods that have had no checkout orders recently.
    • Its colours are screening signals from your own order records, not proof. A quiet method or a pile of unpaid orders is a reason to look, not proof that checkout is down, that a customer was charged or that money was lost. Counts are orders accepted, not money collected.
    • It returns counts, times, fixed summary categories and up to 5 example order numbers per method with their totals and admin links. It never returns customer names, emails or addresses, raw log lines, log file names, background job details, gateway settings, keys or transaction references.

Workflows

A workflow is a recipe: it tells the AI which tools to call, in what order, and how to write up the answer, so you get the same review every week without writing a long prompt.

  • Weekly store review: payment health first, then sales, orders, customers, refunds, top products and channels for the last 7 days against the week before, plus store health and this week’s updates.
  • Revenue drop triage: payment health first, then works out where a drop came from (order count, order value, customers, products, channels) and checks for updates or new PHP errors in the same window.
  • Failed order triage: payment health first, then failed and on-hold orders, the ones to chase first, and a plain warning when failed orders outnumber paid ones (a common sign of card testing or a broken payment gateway).
  • Refund triage: refund rate, the products and countries behind it, and whether it is getting worse.

The weekly review, revenue drop and failed order workflows start with payment health, so a payment problem is the first thing you hear about. Next they check that WooCommerce Analytics data is complete. If Analytics is off, its import hasn’t finished, or recent orders haven’t synced, the AI says so and leaves out the sales figures instead of reporting zeros as fact, but still reports what payment health and the other checks found. Refund triage has no payment step and checks Analytics first. If a step can’t run for your role or your connection, the AI says once which check was skipped and carries on.

Sales analytics (from WooCommerce for Claude)

Totals, breakdowns, trends over time, and order, product and customer rows, from the same data as your WooCommerce Analytics screens. Customers appear as “Customer #N”, never by name. Ranges longer than 365 days ask you to confirm first.

Store and catalogue tools (from WooCommerce for Claude)

Store profile, product search, product details, an AI-readiness score for your catalogue, recommendations, and suggested product improvements. These are read-only too: suggested improvements are text for you to review, not changes.

Who can use which tools

Every tool checks the WordPress role of the person who connected the AI:

  • Workflows and payment health: anyone who can manage WooCommerce (Administrator, Shop Manager). Payment health only reads payment plugin logs (Stripe) and background jobs (Stripe and WooPayments), and only for people allowed to see store diagnostics (Administrators, and Shop Managers if you switch that on); for others those checks show as not checked, and the order checks still run.
  • Sales analytics and store tools: WooCommerce’s own permissions (Administrator, Shop Manager).
  • Store health and update history: Administrators. Shop Managers only if you switch that on in the plugin’s settings.
  • Access check: Administrators only.
  • Customers, Subscribers and other roles get a permission error, never data.

Requires

WordPress asks you to install and activate WooCommerce before this plugin can be activated:

To connect Claude or ChatGPT you also need one connection plugin. This plugin works with either, and no longer needs both installed:

  • Option 1 (recommended): MCP Adapter and Enable Abilities for MCP. Enable Abilities provides the sign-in and connector URL for Claude and ChatGPT, and the switches for which tools are on.
  • Option 2: Easy MCP AI, if you already use it.

This plugin has no sign-in or keys, and registers no REST routes of its own. It registers its tools with the WordPress Abilities API and lets your connection plugin expose them.

Setup

  1. Install and activate this plugin (and WooCommerce, if WordPress asks).
  2. Install a connection plugin if you don’t have one. Option 1 (recommended): MCP Adapter and Enable Abilities for MCP. Option 2: Easy MCP AI.
  3. Open WooCommerce > Blaze MCP Toolkit and read the Setup check. Each line is green, amber or red, with the fix in plain words. It shows the connector URL for the plugin you use.
  4. Option 1: open Settings > WP Abilities and turn on OAuth. For ChatGPT, also turn on “ChatGPT & Other OAuth Connectors”. While you are there, switch off the tools from other plugins you don’t want the AI to use.
    Option 2: tick this plugin’s tools and the WooCommerce Analytics tools under Easy MCP AI › Tools › Abilities, then use Easy MCP AI’s own Connect screen (link on our setup screen). When you click Connect, choose Custom and tick Abilities — Blaze-mcp-toolkit and Abilities — Wc-analytics under Customize permissions. Read-only does not include them.
  5. Add the connector URL in your assistant, if you didn’t use Easy MCP AI’s Connect screen. In Claude: Customize > Connectors > Add > Add custom connector. In ChatGPT: Plugins > Add > Add custom MCP server. Log in to wp-admin in the same browser first, then click Connect and click Allow once.
  6. Ask: “Run my weekly store review.”

Learn to run your store with AI

Storemation is Blaze Commerce’s AI membership for WooCommerce store owners. It includes a lesson on setting up this toolkit, and shows you how to use Claude and ChatGPT for the rest of running your store.

Privacy

  • Payment health returns counts, times, fixed summary categories and a few example order numbers with their totals and admin links. It sends no customer names, emails, phone numbers or addresses, no raw log messages, no gateway settings or keys and no transaction references to the AI.
  • Our diagnostics tools (store health, update history, access check) don’t return customer contact details. They remove emails, phone numbers, card numbers and secrets from log lines, but log lines are free text and may still contain a name someone typed.
  • The sales analytics tools (from WooCommerce for Claude) return totals, counts and, when asked, order rows with customers pseudonymised (Customer #N, never names or emails). They accept location filters such as billing city, state and postcode, but never filters on names or emails.
  • Text that comes from the site (log lines, labels people typed in) is shortened and marked as untrusted, so the AI treats it as data and not as instructions.
  • Each call to our tools is logged for 30 days: time, user ID, tool, a hash of the inputs, row count and duration. No customer data is logged. Store changes (updates, activations) are kept for 180 days.
  • If you use Easy MCP AI, its other tools (such as its general read tool or its WooCommerce tools) can return customer details. The setup screen tells you where to switch them off.
  • The plugin suggests wording for your privacy policy under Settings > Privacy.
  • Nothing is added to your storefront: no scripts, styles or front-end hooks.

Credits

The sales analytics and store tools are the commerce-abilities package from WooCommerce for Claude by Automattic, bundled unmodified under GPL-3.0-or-later (tag v0.4.5, commit cdab921aab8d07ef813121ff78b3558af28f39fa). The four workflows are adapted from WooCommerce for Claude’s workflow prompts and extended with Blaze’s health and update checks. Thank you to Automattic and the WooCommerce for Claude contributors. The bundled files are not edited; Blaze adjusts tool names in instructions to match your connector.

Built by Blaze Commerce, a WooCommerce agency.

WooCommerce is a trademark of Automattic Inc. Blaze Commerce is not affiliated with or endorsed by Automattic, Anthropic or OpenAI.

External Services

This plugin makes no outbound HTTP requests. It does not contact Blaze Commerce or anyone else.

When the store owner connects an AI assistant, the results of the tools the assistant calls are sent to that assistant’s provider as part of the conversation:

What is sent depends on the question asked and the tools switched on. Sign-in (OAuth) and the connection itself are handled by the connection plugin you use (Enable Abilities for MCP and MCP Adapter, or Easy MCP AI), not by this plugin.

Installation

  1. In wp-admin go to Plugins > Add New, search for “Blaze MCP Toolkit for WooCommerce”, then install and activate it. If WooCommerce is missing, WordPress asks you to install and activate it first.
  2. Install a connection plugin (MCP Adapter and Enable Abilities for MCP, or Easy MCP AI), then follow the Setup steps in the Description: open WooCommerce > Blaze MCP Toolkit and add the connector URL in Claude or ChatGPT.

FAQ

Does this plugin change my store?

No. Every tool in this plugin only reads. The AI connection as a whole can include write tools from WooCommerce and your connection plugin (for example, updating an order status). The setup screen lists them and links to where you switch them off.

I use Easy MCP AI. Does this work?

Yes. Install and activate this plugin, then tick this plugin’s tools and the WooCommerce Analytics tools under Easy MCP AI › Tools › Abilities (on a store where Easy MCP AI was set up before this version, newer tools such as the analytics tools and payment health are not ticked for you; the setup screen lists any that are missing, and a workflow says once that it skipped them). Use Easy MCP AI’s own Connect screen (the setup screen links to it) and choose Custom, then tick Abilities — Blaze-mcp-toolkit and Abilities — Wc-analytics under Customize permissions. Read-only does not include them, and Full access turns on Easy MCP AI’s own tools that can change your site. If you approve with nothing ticked, the connection doesn’t finish and your AI app asks you to connect again. The setup screen also tells you how to keep customer details out of AI chats, because some of Easy MCP AI’s own tools can return them.

I have both connection plugins active. Which one is used?

New Claude and ChatGPT connections go through Easy MCP AI, because it takes over the sign-in when it is active. The setup screen shows Easy MCP AI’s connection link and warns you that two are active. A connection made through MCP Adapter and Enable Abilities before Easy MCP AI was active can’t be reconnected while Easy MCP AI is active: make a new connection with Easy MCP AI’s link, or deactivate Easy MCP AI. To use MCP Adapter and Enable Abilities for new connections, deactivate Easy MCP AI.

How do I add it to ChatGPT?

In ChatGPT, open Plugins > Add > Add custom MCP server, paste the connector URL from WooCommerce > Blaze MCP Toolkit, and choose OAuth. With Enable Abilities for MCP, turn on “ChatGPT & Other OAuth Connectors” in Settings > WP Abilities first. In our testing this worked on a Free ChatGPT account.

How do I add it to Claude?

In claude.ai, open Customize > Connectors > Add > Add custom connector and paste the connector URL. The connector then works in Claude on the web, desktop and mobile. Claude may ask you to approve each tool call the first time; that’s Claude’s setting for the connector, not a sign that the tool writes anything.

Connecting fails with a 403 error

A firewall or CDN in front of your site (Cloudflare, Kinsta Bot Protection, a security plugin) is blocking the assistant’s server. With Option 1 (Enable Abilities), add path exceptions for /.well-known/oauth-*, /oauth/* and /wp-json/mcp/*. With Option 2 (Easy MCP AI), add them for /.well-known/oauth-*, /.well-known/openid-configuration, /easy-mcp-ai/*, /wp-json/easy-mcp-ai/*, /authorize, /token and /register. The setup screen lists the exact paths for your connection. Don’t allow it by matching a user agent: that lets anything claiming to be the assistant through.

With Easy MCP AI, your site also fetches the assistant’s sign-in details (for Claude, from claude.ai) while you connect. A firewall or security plugin that blocks your site’s own outgoing requests makes sign-in fail with an invalid_client error: allow outgoing requests to the assistant’s domain.

The sign-in page says the session expired or the state is invalid

Log in to wp-admin in the same browser before clicking Connect, then click the approve button once (Allow with Enable Abilities, Approve & Continue with Easy MCP AI). Clicking it twice shows an error even though the first click worked, so check the connector before trying again.

Why are some tools off for a Shop Manager?

Store health and update history show error logs and plugin details, so they are for Administrators by default. You can let Shop Managers use them with the checkbox on WooCommerce > Blaze MCP Toolkit. The access check lists API keys and app passwords, so it stays Administrator-only. When a workflow skips a step for your role, the AI tells you which check was skipped.

Why does the AI say sales analytics are unavailable?

The analytics tools read WooCommerce Analytics, and the plugin refuses to report numbers it knows are incomplete. There are three usual reasons:

  • Analytics is turned off: WooCommerce > Settings > Advanced > Features.
  • The historical import hasn’t finished: Analytics > Settings > Import historical data.
  • Recent orders haven’t synced because WooCommerce’s background jobs are stalled: check WooCommerce > Status > Scheduled Actions for pending wc-admin jobs.

The Setup check shows which one applies.

I already use WooCommerce for Claude. What happens?

This plugin steps aside for the tools the two share. While WooCommerce for Claude is active, the sales analytics and store tools come from it, and this plugin doesn’t load its own copies, so you won’t see duplicates or conflicts. Store health, update history, access check and the workflows keep working, and a notice on the setup screen explains this.

My host doesn’t give me an error log. Will store health still work?

Yes. The PHP errors section shows amber and says no error log is available, rather than showing green, and the background jobs and updates sections work as normal. Turning on WP_DEBUG_LOG, or asking your host where PHP errors are written, gives it something to read.

Does it work with HPOS?

Yes, with High-Performance Order Storage on or off.

Payment health says a method has gone quiet. Is checkout broken?

Not necessarily. It means the method has taken fewer orders than its own recent pattern would expect for this time of day and week. Holidays, a sale ending, a method you switched off or a quiet week can all do that. Place a small test order with that method, and check the payment plugin’s own dashboard. Payment health never places orders or contacts the provider itself.

Why is payment health unknown for some checks?

Unknown means it couldn’t check, not that everything is fine. Common reasons: fewer than 10 orders in the last 28 days, a payment method whose settlement timing the toolkit can’t confirm (anything other than Stripe card, the card and wallet methods of PayPal Payments, WooPayments and Square, or bank transfer, cheque and cash on delivery), so its unpaid orders are shown as counts without a verdict, logs (Stripe) or background jobs (Stripe, WooPayments) that couldn’t be fully read, a role that isn’t allowed to see store diagnostics, or WordPress not having loaded the payment plugin list (mostly scheduled or command-line runs). In that last case it can’t give an all-clear but still reports any problem it finds, and methods with no recent orders may be left out. Where the log, job or webhook check isn’t supported for a payment plugin it is not run at all, so it never makes a method unknown or green on its own; the answer says it was not checked. It also says which checks were skipped and why.

Changelog

1.2.0

  • New payment health tool: for each payment method, whether it is still taking checkout orders, whether recent checkouts were left unpaid more than usual (judged for Stripe card and the card and wallet methods of PayPal Payments, WooPayments and Square; bank transfer, cheque and cash on delivery skip it; other methods show the unpaid counts without a verdict), whether the payment plugin failed background jobs (Stripe and WooPayments), and whether it logged errors or recorded webhook delivery problems (Stripe only). Checks a plugin isn’t supported for are not run and don’t count either way. Ask-only: it never changes orders, settings or payments and never contacts a payment provider.
  • Every check says red, amber, green or unknown, whether it was checked and how complete its evidence was. Unknown is reported as a gap, never as healthy.
  • Payment plugin logs (Stripe) and background jobs (Stripe and WooPayments) are only read for those plugins, and only for people allowed to see store diagnostics. The order checks work for anyone who can manage WooCommerce.
  • The weekly review, revenue drop and failed order workflows now start with payment health. If WooCommerce Analytics is unavailable they skip only the Analytics steps and still report the payment findings.
  • On an existing Easy MCP AI connection, tick payment health under Easy MCP AI › Tools › Abilities. The setup screen lists it until you do.

1.1.0

  • Works with Easy MCP AI as well as MCP Adapter with Enable Abilities for MCP. You only need one of them.
  • The setup screen now checks and explains the connection plugin you actually use, with its own connector URL and steps.
  • Workflows now name the right tools for the connection they are used through.
  • Fixed the confirmation prompt for ranges longer than 365 days so it names the correct tool.
  • Privacy text and readme now cover both connection plugins.

1.0.0

  • First release.
  • Store health, update history and access check tools.
  • Weekly store review, revenue drop, failed order and refund workflows.
  • Setup check screen with fixes for each step, and a privacy warning for other tools that return customer details.
  • Bundles the commerce-abilities package from WooCommerce for Claude by Automattic (https://github.com/woocommerce/woocommerce-claude, GPL-3.0-or-later), version 0.4.5, commit cdab921aab8d07ef813121ff78b3558af28f39fa, unmodified. It provides the wc-analytics tools and the store knowledge tools.