| 开发者 | blazecommerce |
|---|---|
| 更新时间 | 2026年11月8日 10:52 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
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): 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): 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.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.
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.
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, the analytics tools are not ticked for you; the setup screen lists any that are missing). 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.
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.
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.
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.
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.
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.
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.
The analytics tools read WooCommerce Analytics, and the plugin refuses to report numbers it knows are incomplete. There are three usual reasons:
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.
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.
Yes, with High-Performance Order Storage on or off.