MCP for WooCommerce: How to Connect Claude to Your Store

MCP for WooCommerce is possible today: WooCommerce has built-in MCP (Model Context Protocol) support that lets an AI assistant such as Claude list products and orders on your store. The catch is that WooCommerce describes this support as a developer preview, so details can change. This guide explains what exists, how to connect Claude step by step, and where it breaks.

If MCP is new to you, start with What Is MCP? A Plain-English Guide for E-commerce Merchants. In short: MCP is an open protocol that lets an AI assistant connect to tools and data through a standard interface. An MCP server exposes the tools, and an MCP client (Claude) uses them.

What does MCP for WooCommerce look like today?

There are two layers, and it helps to keep them apart.

The WordPress layer. WordPress 6.9 (released December 2, 2025) includes the Abilities API in core. It is a registry of typed, permission-checked actions that plugins can declare. The official MCP Adapter, built by the WordPress AI Team, turns those abilities into MCP tools, resources and prompts. The adapter has no AI features of its own: what Claude can do depends on which abilities your site registers.

The WooCommerce layer. According to the WooCommerce developer docs, WooCommerce builds on the Abilities API and the MCP Adapter. Early documentation covered product management (list, get, create, update, delete) and order management (list, get, create, update), implemented by bridging to existing REST API endpoints. The beta first appeared in WooCommerce 10.3 as an opt-in feature flag.

Some third-party guides claim that a later release added a fixed set of "domain abilities". I could not confirm that against a WooCommerce primary source, so check the release notes for your installed version.

Which connection options exist?

Path	Works with	Status	Main limit
WooCommerce MCP (native) with MCP Adapter	Claude Desktop, Claude Code via local proxy; Claude custom connector if publicly reachable	Developer preview	Endpoint and authentication may change
WordPress MCP Adapter alone (self-hosted)	Same as above	Shipping (version 0.7.0 at the time of research)	Needs WordPress 6.9 or newer and abilities
WordPress.com official Claude connector	Claude (Browse connectors)	Shipping since February 2026	For WordPress.com accounts, not a typical self-hosted store
Community plugins and "WooCommerce for Claude"	Varies	Experimental or third party	No stability guarantees

"WooCommerce for Claude" (May 2026) was published as an experiment to gather feedback, not as a product. Treat it as a test bench.

What do you need before you start?

• A staging copy of your store. Do not experiment on live data first.
• WordPress 6.9 or newer, and a current WooCommerce version.
• Admin access to install plugins and change feature settings.
• A Claude account and one of: Claude Desktop, Claude Code, or a plan that supports custom connectors.
• Someone comfortable with Composer or WP-CLI if you go the developer route.

How do you connect WooCommerce to Claude, step by step?

These steps follow the official WooCommerce and WordPress documentation as of October 2026. Menu names and endpoints in a developer preview can change, so confirm each against the live docs.

1. Back up and clone. Create a staging site with a copy of your catalog. Real customer data on staging should be anonymized where possible.
2. Update WordPress and WooCommerce. The MCP Adapter requires WordPress 6.9 or newer.
3. Install the MCP Adapter. Composer is the primary install method. The plugin is also listed at wordpress.org/plugins/mcp-adapter. On 6.9 or newer you do not need to install the Abilities API separately.
4. Enable WooCommerce MCP. In the original beta this was a switch at WooCommerce > Settings > Advanced > Features, labelled "Enable MCP Beta". Newer versions may label it differently.
5. Create a dedicated user. Make a separate WordPress user with the narrowest role that works. The adapter acts as the WordPress user you authenticate as, so that user's permissions are Claude's permissions. For self-hosted sites, application passwords are the usual credential.
6. Find the current endpoint and authentication. The WooCommerce endpoint has been documented as /wp-json/woocommerce/mcp. However, the current docs include a section on a deprecated WooCommerce MCP endpoint that used WooCommerce REST API keys. Many older tutorials still show that key-based flow. Follow the live WooCommerce docs and the adapter's authentication requirements, not an old blog post.
7. Connect Claude using one of the options below.
8. Run a read-only test. Ask Claude to list five products or show yesterday's orders. Do not ask it to change anything yet.

Claude Desktop and Claude Code (local proxy)

The official WooCommerce tutorial series (part 1 was published in April 2026) shows a local flow: Claude talks to a small proxy called mcp-wordpress-remote over stdio (a local process connection), and the proxy talks to your site over HTTP. This works with a staging site on your own machine or network because the proxy runs on your device.

For developers, the adapter also has a STDIO transport. One third-party guide shows wp mcp-adapter serve through WP-CLI for local Claude Code use. Verify the exact command in the adapter's own documentation.

Claude custom connector (claude.ai, Desktop, mobile)

Claude supports remote MCP servers as custom connectors. On Pro and Max plans the path described by Anthropic is Customize > Connectors > Add > Add custom connector. On Team and Enterprise plans an Owner adds it under Organization settings > Connectors, and members then click Connect. Anthropic has renamed menus before, so follow its current support article.

The key limit: Claude connects from Anthropic's cloud, not your device. The server must be reachable on the public internet. Localhost, VPN-only and firewalled sites will not connect. Your store also needs HTTPS and a way to authenticate that Claude can use. A custom connector has a request headers field for fixed credentials such as a bearer token, but confirm that your WooCommerce authentication method works with it before relying on it.

What is the WordPress Abilities API and why does it matter?

The Abilities API is how a WordPress site says "here is something an AI can do, and here is who may do it". Each ability has a name, defined inputs and outputs, and a permission check.

For MCP, one rule matters most: abilities are private by default. A plugin must mark an ability as public for MCP before it appears. The adapter then reaches abilities through three general tools: discover abilities, get ability info and execute ability.

For a merchant, this means the exposed surface is a deliberate choice. If a plugin does not register abilities, Claude cannot see its data. For agencies, it means custom abilities (for example a stock report) are possible, but WooCommerce's own demo plugin is marked "not production ready", so do not ship it to clients.

What about the WordPress.com connector?

WordPress.com launched an official Claude connector in February 2026, secured with OAuth 2.1 (a standard sign-in flow, so no password is pasted into Claude). You enable MCP in your WordPress.com account, then add WordPress.com from Claude's connector directory. The Claude listing mentions 60 or more abilities and confirmation of every change, on paid WordPress.com plans.

It targets WordPress.com sites. If you run WooCommerce on your own hosting, you will usually use the adapter route above. Check WordPress.com's documentation to see whether your plan exposes store data.

How do you keep it safe?

• Start read-only. Use a user role that cannot edit products or orders, so a mistaken request fails.
• Use staging first, then production with a limited user.
• Never share administrator credentials. Revoke the application password when you finish testing.
• Review every write action before approving it. Price changes and order edits are hard to undo in bulk.
• Remember that product text and customer notes are data Claude reads. Treat them as untrusted, since hidden instructions inside content (prompt injection) are a known risk.

What can go wrong?

• Connection fails on a custom connector. Your site is probably not publicly reachable, or a firewall or security plugin blocks the request.
• Authentication errors. You may be following the deprecated key-based flow. Check the current docs.
• No tools appear. The abilities are not public for MCP, or the feature switch is off.
• Behavior changes after an update. The Abilities API and WooCommerce MCP are still evolving, so pin versions and retest after updates.
• Wrong or partial answers. Claude only sees what the abilities return. Large catalogs may return partial lists.

What can it not do?

It does not replace your analytics, ad platforms or your store's reporting. It reads and changes only what the registered abilities allow. It does not give you a hosted, supported WooCommerce product with guarantees while the feature is in preview. For how this differs from direct API work, see MCP vs API: What Changes for Online Stores and Agencies.