Claude and WooCommerce: what the MCP connector can do

By Abdalla Kamesh · Published October 22, 2026 · 7 min read

“MCP” and “connector” are words that developers use, so this post starts with what they mean for a store owner. An MCP endpoint is an address that an AI assistant can talk to with a fixed set of actions. StoreToNative has one (the address is in the setup steps below). Point your own Claude, Codex or Cursor at it and you can talk to your app in plain words: “how did my app do this week?”, “send a push to shoppers with a cart”, “make my colors match my new logo”.

It is on the Pro and Agency plans at no extra cost. It uses your own AI, so nothing is metered on our side. This post is what it can do, how to set it up, and the limits, in that order. Every fact here comes from the Connect your AI help page, which is the page to keep open while you do it.

Three conversations that work today

“How did my app do this week?” Your AI reads revenue, orders, installs, top products and the carts sitting abandoned, for 7, 30 or 90 days, plus recent orders and your weekly brief. It answers with numbers it read, not numbers it guessed. About your shoppers it sees counts and totals; for a recent order it sees the number, total, status and item count, never who placed it or what was in it.

“Send a push to shoppers with a cart.” Your AI writes the push, picks the audience (everyone, or one of your audiences, such as shoppers with a cart), shows you the reach, and asks before it sends. It can schedule a push for later, and cancel a scheduled one that has not gone out yet. Afterwards it can tell you how each push did: when it went out, how many devices it was sent to and how many times it was opened. Pushes keep the usual limit of 60 an hour. For what to write, push notification copy that people actually tap still applies: your AI never invents an offer, a price or a date.

“Make my colors match my new logo.” Design is where the connector is most useful and most careful. Ask for a theme change, a new home section, a different bottom bar or new first-run slides. Your AI makes a draft first: a draft link shows the change on a live preview of your app and changes nothing until you say yes. A draft link works for up to 24 hours; a preview link after a saved change works for up to 30 days. Saved changes reach installed apps over the air, within a launch or two, with no rebuild and no store re-review. OTA, explained covers what travels that way.

Every design change your AI saves is kept with its before and after in App Builder → History, and one press on Revert puts it back. You can also ask your AI to undo its last change. If that part of the app was changed again later, the revert is refused and nothing moves.

Beyond those three, your AI can find products and categories by name (so it puts the right ones on your home screen), turn add-ons and the thank-you, win-back and VIP automations on or off, check the store connection and start a sync, open a support ticket with what it found, and tell you what still blocks the App Store and Google Play. It also has eight guided workflows in its prompt menu, from Weekly review to Monthly client report (Agency plan), and it can read the help pages.

The address of the connector, for every tool below:

https://api.storetonative.com/v1/api/mcp

In Claude, open Customize, then Connectors. Press + and choose Add custom connector.
Paste the address above and press Add.
Press Connect. Sign in with your StoreToNative account and press Approve.
In a chat, press +, then Connectors, and turn StoreToNative on. Ask it to list your StoreToNative apps.

The Approve page shows the name of the app that is asking. If you do not know it, press Deny. Apps you approved are listed in Settings → Connected AI apps, each with a Disconnect button that works at once.

Setup with an API key: Claude Code, Codex, Cursor

Tools that take a key use the same address with a key you create under Developer → Webhooks & API → API keys. Pick one app as the key’s scope if you want the AI kept to that app; an Agency workspace with five client apps will want that. The Connect your AI card on the same page has the setup lines to copy for each tool.

In Claude Code, one line:

claude mcp add --transport http storetonative https://api.storetonative.com/v1/api/mcp --header "Authorization: Bearer YOUR_KEY"

In Codex, a block in ~/.codex/config.toml with the key in a shell variable:

[mcp_servers.storetonative]
url = "https://api.storetonative.com/v1/api/mcp"
bearer_token_env_var = "STORETONATIVE_KEY"

In Cursor, an entry in ~/.cursor/mcp.json (or .cursor/mcp.json in one project) with the same address and an Authorization: Bearer YOUR_KEY header. Do not commit a project file that has your key in it. Any other app that supports MCP takes the same address and header.

Whichever tool you use, the first check is the same: “list my StoreToNative apps”. Revoking the key in API keys disconnects that tool at once, on any plan.

The limits, stated plainly

Your AI can only do what your own role can do. A read-only client login gives a read-only AI.
Design changes show after two restarts. The app downloads the change on one launch and shows it on the next. Your AI gives you a preview link so you can look before your shoppers do.
Sending a push has no dry run. Your AI shows the reach and asks first, but a sent push cannot be undone. Drafts exist for design, not for pushes.
Daily limits per key: 120 app changes, 60 draft links, 5 support tickets; 6 store syncs a day per app. One connection can make 300 requests a minute; over that, the AI is asked to wait.
What stays in the console: publishing, billing, your team, your keys and your store credentials. The AI never touches them.
Scheduled runs are not verified. Some AI apps can run a request every Monday. We have not yet confirmed that such a run works without you present; ask the same question yourself on Monday and the answer is the same.

Security notes

The connector talks to the same StoreToNative API as the console, with the same plan gate and role check; the AI does not get a side door. Every change it makes is saved in your workspace’s activity log. A password reset, or Sign out other devices on the Account & security page, disconnects every approved AI app. Signing out of the console does not.

What your AI reads is handled under your AI provider’s terms, which is the one part of this we cannot change. If that matters to you, create a key scoped to one app, and revoke it when the job is done.

Who it is for

Store owners who already run their week through an AI assistant and want the app’s numbers and a push inside that same conversation. Agencies on the Agency plan, where “make this month’s report for my client” is a one-line request. And developers who would otherwise have written against the WooCommerce REST API to get the same numbers. If none of that is you, the console does everything the AI does, with buttons.

Related reading

The connector is included on the Pro and Agency plans. Setup, the full action list and the limits are on the Connect your AI help page.