Your store’s numbers are all in WooCommerce. Getting to them means logging in, opening the right tab, maybe exporting a report. Connect Claude to your store and that flips: you ask, it answers from your real data, and the setup takes a few minutes with zero code.
This is the no-code walkthrough: install, one approval click, prove it works with your real orders, and set the guardrails that make write access a deliberate choice. Everything below works with the WooCommerce plugin you already run; your payment gateway keeps doing its job untouched.
What you’re connecting (the 30-second version)
Two pieces, one conversation. Your store gets an MCP server through the free Easy MCP AI plugin, which gives Claude a secure way to read and manage store data. MCP (Model Context Protocol) is just the common language they speak. Claude, or any MCP-compatible assistant, is the client that connects to it.
Transparency note: Easy MCP AI is built by ThemeIsle, the same company behind this blog. It has 10,000+ active installs and holds a 5.0 out of 5 rating from 8 ratings as of September 2026. Free on WordPress.org, no second subscription.
Step 1: Install the plugin and enable the WooCommerce integration
Start in your WordPress admin under Plugins → Add New, search for “Easy MCP AI,” and install and activate it. Then open the new Easy MCP AI menu and go to the Plugins tab. You’ll see a WooCommerce row showing the integration is stable, with an enable toggle and the tool count right beside it: 46 tools, 23 read and 23 write.
Flip it on. That’s the moment your store becomes readable (and, if you later allow it, manageable) by your AI.
Step 2: Connect Claude with one approval click
On the Easy MCP AI Dashboard, copy your store’s MCP address (it’s front and center). In Claude on your desktop, add a custom connector and paste it in. Your browser opens a consent screen on your own site: sign in, tick what Claude is allowed to do, and approve.
The ticks are per scope, so “read orders and reports” can be granted without “write products.” For the first week, tick read-only. You can widen it later from the same place, and every connection can be revoked whenever you want.
Worth pausing on what just happened: that consent screen is OAuth running on your site, not on a third-party service. Your WordPress login never leaves your store, and the client receives a token limited to exactly the boxes you ticked. If you later change your mind, deleting the connection on the dashboard revokes the token in one click.
Step 3: Prove it with one commerce question
One question settles whether the loop works. Ask Claude: “List today’s orders.” If the answer comes back with your real order numbers, dates, and totals, your store and Claude are on speaking terms. Follow with “and the total revenue for those?” for the satisfying version.
If you’d rather keep the chat entirely read-only for now, that’s fine too: the same question answers from the read scope alone.
Ten questions worth asking on day one
Once the loop is proven, these are the commerce questions that make the connection earn its keep. All of them work on read-only access:
- “List today’s orders, with totals.”
- “What’s our revenue this week compared to last week?”
- “Any orders stuck in pending payment?”
- “Show me recent refund requests.”
- “Which products are low on stock?”
- “What are the ten best sellers this month?”
- “Who are our top customers by lifetime spend?”
- “Any failed payments worth following up on?”
- “What’s the average order value this month?”
- “Which coupons were used most this week?”
Notice what none of them need: exports, spreadsheets, or clicking through four admin tabs. You ask in plain English, the answer comes from your live store data, and the follow-up question is free.
Connecting Cursor, ChatGPT, or Gemini instead
The MCP address you copied isn’t Claude-specific. Any MCP-compatible client connects the same way: paste the address, approve on your site’s consent screen, start asking. Every major MCP client has a place to add a server by URL; the exact label differs (MCP settings, connectors, integrations). Whichever client you pick, the store side stays identical: same MCP address, same consent screen, same per-scope ticks. The Dashboard shows per-client connection configs, and the setup guides for each major AI walk through the clicks per client.
Two practical notes. Each client gets its own approval and its own scope, managed individually on the same dashboard, so a coding assistant in Cursor can stay read-only while your main Claude connection earns wider access later.
Set your guardrails
Three minutes of setup that turn “an AI can see my store” from a worry into a routine:
- ✅ Scoped access. Tokens and OAuth approvals use a checkbox permission tree, so you grant exactly the tools you mean to grant, per content type, with read-only as a first-class option.
- ✅ Sane defaults. Every tool call passes a WordPress capability check, and a per-token rate limit (60 requests per minute by default, configurable) keeps batch jobs paced.
- ✅ Full visibility. Every action is written to the Audit Log with the token, arguments, result, and client IP, and every change the AI makes gets a before-and-after snapshot in Change History. An optional IP whitelist can restrict which addresses may use your MCP endpoint at all.
When it won’t connect (the usual three causes)
The site isn’t reachable from the client. Claude talks to your site directly, so anything that blocks it (basic auth on staging, a local-only install, a firewall rule) stops the handshake. Fix: use a reachable URL or relax the rule for your MCP path.
The wrong address. The endpoint must be your site’s MCP address exactly as shown on the Dashboard, including the full path. A missing character gets you silence, not an error message.
A permission mismatch. If a write request fails while reads work, your token or consent is read-only by design (probably your own week-one setting). Widen the scope deliberately, or stay read-only and enjoy the answers.
💡 Tip: after a quiet read-only week, check the Audit Log once. Seeing every action the AI took, in plain rows, is what makes people comfortable granting more later.
The first week, done right
Days one to three: ask questions only. Orders, revenue, top sellers, “any refunds pending?” Days four to seven: keep the questions coming and skim the Audit Log once. End of week one: decide which single write capability (if any) earns a scope upgrade. Draft product descriptions and coupon setup are the usual first candidates; order writes can wait until the trust is boring.
📖 You might also like to read: how to manage your WooCommerce store with AI, covering the workflows that make the connection pay once you’re live.
The bottom line
Connecting Claude to your WooCommerce store is three steps and a consent click: install Easy MCP AI, enable the WooCommerce integration’s 46 tools, approve the connection, and ask for today’s orders. Read-only first, widen deliberately, and let the log keep everyone honest. The whole setup is reversible in one click, which is exactly how store tooling should behave.
Does this cost anything?No. Easy MCP AI is free on WordPress.org with no second subscription. Claude or your chosen AI has its own pricing, but the store connection itself is free.
Does it change my Stripe or checkout setup?Not at all. The connection reads and manages WooCommerce store data only. Your payment gateway, checkout forms, and card handling stay exactly as they are.
Does this work with ChatGPT or Gemini too?Yes. Any MCP-compatible client connects the same way: paste your store’s MCP address, approve, and start asking. The Dashboard shows per-client connection details for each major AI.