How to Connect WooCommerce to Claude with MCP (2026 Guide)

WooCommerce runs a big share of the web's stores, and it's built on WordPress, so connecting it to Claude follows the WordPress path, not the Shopify one. The good news: there's an official server from the company that makes WordPress, and the setup is mostly a config file and an API key, no plugin to build.

This guide walks through it end to end: create a REST API key, pick an MCP server, wire it into Claude Desktop, and scope it so Claude can help without putting your store at risk. Steps here were checked against WooCommerce's REST API docs and the PulseMCP directory on July 9, 2026.

If you're on Shopify instead, we have a separate guide for connecting Shopify MCP to Claude. The shape is similar; the token step differs.

Jump to:

• What "WordPress MCP" means for a WooCommerce store
• Prerequisites
• Step 1: create a WooCommerce REST API key
• Step 2: choose a WordPress or WooCommerce MCP server
• Step 3: register the server in Claude Desktop
• Step 4: verify the connection
• Keep it safe
• Common snags

What "WordPress MCP" means for a WooCommerce store

A quick clarification, because the naming trips people up. WooCommerce is a plugin on WordPress, so most MCP servers in this space are WordPress MCP servers that also expose WooCommerce data. When you see "WordPress MCP," assume it covers your store's products and orders too, as long as the server lists WooCommerce tools.

That's why the official option here comes from Automattic, the company behind WordPress and WooCommerce, rather than from a standalone WooCommerce vendor.

Prerequisites

• A WooCommerce store you have admin access to.
• Claude Desktop. This route uses the desktop app's config file, so you don't need a terminal.
• Node.js 18 or higher, if your chosen server runs through npx. Most do.

Step 1: create a WooCommerce REST API key

This is how Claude authenticates to your store. WooCommerce generates the credentials for you.

• In WordPress admin, go to WooCommerce, then Settings, then Advanced, then REST API.
• Click Add key.
• Enter a Description like "Claude MCP" so you recognize it later.
• Pick the User the key acts as, and choose a Permissions level: Read, Write, or Read/Write. Start with Read.
• Click Generate API key.

WooCommerce shows a Consumer key and a Consumer secret. The secret appears only once, so copy both somewhere safe before you leave the page. If a key ever leaks, this same screen has a Revoke link.

Step 2: choose a WordPress or WooCommerce MCP server

You don't build the server; you pick one that already speaks the WooCommerce REST API.

Automattic WordPress Remote (official). From the company that builds WordPress and WooCommerce, this bridges your site and WooCommerce data to a local client over the REST API. It's the maintained, first-party choice, and the one to try first.

WooCommerce by AmitGurbani (community). A deeper community build with 101 tools spanning products, orders, customers, coupons, and shipping. Reach for it when you want Claude running the whole store, not just reading it.

Respira for WordPress (official). A WordPress MCP with native page-builder editing and WooCommerce tools, useful if you also want Claude touching content and layout, not only commerce data.

Whichever you choose, get the exact run command and the env variable names from that server's own page. They vary by project, and copying the wrong variable names is the most common reason a connection silently fails. We compare the strongest options in our roundup of the best MCP servers for Shopify and WooCommerce.

Step 3: register the server in Claude Desktop

Now you tell Claude how to launch the server and pass it your key.

Open the config file: in Claude Desktop, go to Settings, then Developer, then Edit Config. That opens claude_desktop_config.json. Add your server under mcpServers. The shape looks like this, with the package name and env keys filled in from the server you chose:

{
  "mcpServers": {
    "woocommerce": {
      "command": "npx",
      "args": ["-y", "the-woocommerce-server-package"],
      "env": {
        "WOOCOMMERCE_SITE_URL": "https://your-store.com",
        "WOOCOMMERCE_CONSUMER_KEY": "ck_your_consumer_key",
        "WOOCOMMERCE_CONSUMER_SECRET": "cs_your_consumer_secret"
      }
    }
  }
}

Match the env variable names to your server's docs rather than copying these verbatim; each project names them slightly differently. Save the file and fully quit and reopen Claude Desktop, since it only reads the config at launch.

Step 4: verify the connection

Open a new chat and ask something only the store can answer, like "list my five most recent WooCommerce orders." If Claude returns real orders, you're connected. If it says it has no such tool, the config didn't load, so recheck the JSON for a typo and restart the app.

Try a read before any write: "which products had the fewest sales last month" is a good first prompt. It proves the connection and gives you something useful without changing anything.

Keep it safe

An API key with Write permission can change your store, so treat this like giving out a set of keys.

• Start Read-only. Generate a Read key first. It can report and analyze but can't alter products or orders.
• Test on staging. Point the server at a staging copy of your site, run your riskier prompts there, and only switch to the live key once you trust it.
• Grant Write deliberately. Move to a Read/Write key only when you have a specific job for it, and keep a Read-only key around for everyday questions.
• Revoke when done. If you stop using the integration or the secret leaks, revoke the key from the same REST API screen and generate a fresh one.

Common snags

• "No such tool" in Claude. The config didn't load. Check claude_desktop_config.json for a JSON syntax error, then fully restart Claude Desktop.
• 401 or authentication errors. The Consumer key or secret is wrong, or the site URL is off. Re-copy both from WooCommerce, and confirm the URL includes https://.
• Connects but returns nothing. Your key may be Read-only while you're asking for a write, or the server's WooCommerce tools aren't enabled. Check the server's tool list.
• Works locally but not remotely. Some servers assume a reachable site URL. A local-only dev site behind no public URL can't be reached by a hosted server.

Where this leaves your store

Connecting WooCommerce to Claude turns your store into something you can run by asking. The harder question sits one level up: when a shopper asks an AI what to buy, does it recommend your store at all?

Wiring up MCP is the plumbing. Being the store an assistant names is the goal, and that's a measurement problem first. New to the protocol? Start with what the Model Context Protocol is and why it matters for stores. Ready to make your store easier for AI to recommend? Read how to optimize your store for ChatGPT Shopping.

Is AI recommending your store? Check free.

Frequently asked questions

Is there an official WooCommerce MCP server?

Automattic, the company behind WordPress.com and WooCommerce, ships an official WordPress Remote MCP server that bridges WordPress and WooCommerce data to local clients through the REST API. There are also strong community servers, like AmitGurbani's WooCommerce build with 101 tools.

Do I need to code to connect WooCommerce to Claude?

No coding, but you do edit one config file. You create a WooCommerce REST API key in your dashboard, then add the MCP server to Claude Desktop's claude_desktop_config.json with that key. No plugins to build and no terminal commands beyond restarting Claude.

What can Claude do with my WooCommerce store once it's connected?

With a Read key, Claude can pull products, orders, customers, and reports in plain language. With a Read/Write key, it can also create and update data, like editing a product or updating an order, depending on the tools the server exposes.

Is it safe to connect my live WooCommerce store to Claude?

Treat it like any integration. Create a Read-only key first, test on a staging site, and grant Write access only when you need it. Store the Consumer secret safely, and revoke the key from the REST API screen if it is ever exposed.