If you’re weighing StoreAgent vs WooCommerce core MCP, you’ve almost certainly asked the obvious question first. WooCommerce ships its own MCP server now. It’s free, it’s first-party, it’s already sitting in the plugin you’re running. Why pay anyone for a connection your store can make on its own?
It’s a fair question and it deserves a straight answer. Here’s the part the feature announcement doesn’t lead with: the built-in MCP integration is still labelled a developer preview in WooCommerce’s own documentation, it asks you to test on a staging site rather than a live store, and connecting a remote client means running a Node.js proxy on your machine, creating a WordPress Application Password, and hand-editing a JSON config file.
So StoreAgent vs WooCommerce core MCP isn’t really two products competing. Both are built on the same WordPress Abilities API, and core MCP is the foundation the whole platform is heading toward. The choice is between a developer feature you wire up yourself and a managed connection a store owner can switch on today. This comparison covers how ready each one is, what it takes to connect, what your assistant can actually do once it’s in, and what you’d pay.
StoreAgent Vs WooCommerce Core MCP: The Short Answer
StoreAgent is the better choice for a store owner who wants this working today, because the connection is a managed gateway: nothing runs on your site, there’s no Application Password to create, no proxy to install, and MCP is included on the free plan. WooCommerce core MCP is the better choice for a developer who wants first-party plumbing with no third party in the path, and who is happy on a staging site while the preview label is still there.
Core MCP is not a weak product. It’s an early one, by design, and Automattic says so plainly. It also isn’t a competitor in the usual sense: StoreAgent registers its abilities through the same WordPress Abilities API that core MCP exposes, so the two end up complementing each other more than they collide.
| Comparison Factor | StoreAgent | WooCommerce core MCP |
|---|---|---|
| Release status | Live since plugin 1.1.9 | Documented: developer preview, APIs may change |
| Where the server runs | StoreAgent’s cloud gateway, nothing on your site | An endpoint on your own store |
| Remote client setup | Paste an endpoint, approve in wp-admin | Node.js proxy, JSON config, Application Password |
| Credential | OAuth sign-in on your own store, short-lived tokens | WordPress Application Password in a local file |
| Store data abilities | Content, AI memory, chat and plan, plus any ability your store registers | Seven canonical product and order abilities |
| Product create, update, delete | Through WooCommerce’s own abilities on the same connection | Yes, built in |
| Access control | Read-only or read-write scope, one-click revoke, activity log | Per-ability permission callbacks, no revoke UI |
| Beyond MCP | Storefront chatbot, content agents, store insights | None, MCP only |
| Price | Free plan, then $19 to $249 a month | Free, part of WooCommerce core |
Is WooCommerce Core MCP Ready For A Live Store?
Not yet, and that isn’t our opinion. The WooCommerce developer documentation opens the MCP page with a notice saying the implementation “is currently in developer preview” and that “implementation details, APIs, and integration patterns may change in future releases as the feature matures”. The same page closes with an Important Considerations block listing breaking changes as a possibility, telling you to test thoroughly before deploying to production, and noting that the WordPress Abilities API and the MCP adapter are both still evolving. The launch announcement lists a staging site as the first prerequisite, ahead of the software versions.
That label has been there a while. The MCP beta shipped in WooCommerce 10.3, the stack firmed up with WooCommerce 10.7 and WordPress 6.9, and WooCommerce 10.9 replaced the first REST-derived bridge with a proper set of canonical domain abilities. I checked the documentation page again on the day this went out and the developer preview notice was still at the top of it.
One thing worth noticing about that history: the original endpoint is already deprecated. Integrations built against /wp-json/woocommerce/mcp in the beta now point at the shared WordPress adapter endpoint instead, and the old one is kept only as a compatibility path. That is exactly the kind of churn a preview label is there to warn you about, and it is a good reason to keep it off a store that takes money.
StoreAgent’s WooCommerce MCP server sits in a different place on that curve. It went live in plugin version 1.1.9, it’s documented for store owners rather than for contributors, and the connection is versioned and maintained by us rather than by your own config file.
What It Takes To Connect Each One
This is where the two diverge hardest, and it has nothing to do with quality. Core MCP is a developer feature and it reads like one.
To connect a remote client to core MCP, its documentation asks you to: turn on the mcp_integration feature flag, either from WooCommerce settings or by running a WP-CLI command; create a dedicated WordPress user with minimum capabilities; generate an Application Password from that user’s profile screen; confirm the site is on HTTPS with non-plain permalinks; install Node.js 22 or later; and add a block of JSON to your MCP client’s config declaring an npx command that pulls the @automattic/mcp-wordpress-remote proxy. The documentation then warns you not to commit that config to version control, because your Application Password is sitting in it in plain text.
None of that is hard for a developer. All of it is a wall for the store owner who just wants Claude to tidy up twelve product descriptions.
StoreAgent’s side is three steps in the browser: update the plugin, switch MCP on under StoreAgent then Settings then MCP, and copy your endpoint. You paste that endpoint into your assistant as a custom connector, your own store opens its approval page in wp-admin, you sign in there as an administrator or shop manager, and you pick read-only or read-write. Read-only is pre-selected. No proxy, no Node version, no password in a file.
I ran a connection like that against a WooCommerce test store while writing this and asked the assistant for its in-stock products. The reply came back with SKUs, stock counts and live prices in the store’s own currency, and I never opened a terminal to get it. I asked the same connection for the site’s runtime details and it reported the WordPress, PHP and database versions straight back. That is the whole setup difference in one paragraph.
What We’ve Seen: Store owners read “WooCommerce has MCP built in” and assume it’s a setting they switch on, the way they switched on HPOS. Then they hit npx, an Application Password and a JSON file, and the project quietly dies in a browser tab. The question to ask isn’t “does my platform support MCP?” It’s “what do I personally have to run, secure and keep updated to use it?”
There’s a security shape to this too. With core MCP, the credential is a long-lived Application Password stored on a laptop, and the documented way to limit blast radius is to create a restricted WordPress user. With StoreAgent, the store never runs an MCP server at all: the public connection ends at our gateway, which handles authentication, scope and rate limiting, then calls your store with the same permission checks wp-admin uses. Access is scoped at approval time, write tools are hidden entirely from a read-only connection, every write asks you before it runs, every call lands in a 30-day activity log in wp-admin, and any connection can be revoked in one click.
Core MCP logs to WooCommerce, then Status, then Logs under the source woocommerce-mcp. That’s a log file, not an audit trail with a revoke button, and its own documentation warns that order and customer operations “may expose personally identifiable information (PII) including names, email addresses, physical addresses, and payment details”.
What Your Assistant Can Actually Do In Your Store
Both sides are built on the same foundation. The WordPress Abilities API landed in WordPress 6.9 as a standard registry of named, permission-checked actions that external systems such as AI agents can discover and run, and both StoreAgent and WooCommerce register into it. MCP itself is an open standard for connecting AI applications to external tools, so neither side is inventing a protocol.
What differs is the menu.
WooCommerce 10.9 introduced a canonical set of seven domain abilities: query products, create a product, update a product, delete a product, query orders, update an order status, and add an order note. They’re well built. Product delete sends the product to trash unless you force it, order status updates reject a no-op, and order notes are attributed to the acting user. But the scope is product and order plumbing and nothing else. No customers, no coupons, no refunds, no shipping or tax, no reports, no content generation, no chat.
There’s also a wrinkle worth knowing before you plan a workflow around it. On the shared adapter endpoint, WooCommerce doesn’t register one MCP tool per ability. The adapter exposes three generic tools instead, for discovering abilities, reading an ability’s details and executing one, and your assistant works through those. It functions, but it means the assistant is navigating a directory rather than reading a purpose-built toolbox.
StoreAgent’s WooCommerce AI abilities are a different shape because they’re built for store work rather than for data access. They cover content generation (product descriptions, tags, image alt text, review summaries, coupons and coupon descriptions, upsell and cross-sell suggestions), AI memory management (sync status, what’s indexed, what failed and why, triggering a re-sync), the WooCommerce AI chatbot itself (widget configuration, escalation settings, reading conversations), and your plan usage.
Now the part that matters most for this comparison, and the reason “which one wins” is the wrong frame. Any ability your store registers can be exposed through the StoreAgent connection, including WooCommerce core’s own. When I queried products through that test connection, the filters the assistant was offered were WooCommerce’s canonical product type aliases, the exact physical, virtual, digital, affiliate and grouped list from the 10.9 ability set. Core’s abilities were running through the managed gateway, next to StoreAgent’s, with no proxy and no Application Password anywhere in the chain. Third-party abilities are off by default and you allowlist each one, so nothing appears in your assistant that you didn’t switch on.
Read that together and the split is clear. Core MCP gives an assistant hands on your products and orders. StoreAgent gives it hands on the work.
How StoreAgent And WooCommerce Core MCP Pricing Compare
This is the easiest section to write honestly, because one side is free. WooCommerce core MCP costs nothing. It ships inside WooCommerce, there’s no add-on to buy, and there’s no metering on how many calls your assistant makes. Your only running costs are the MCP client subscription and whatever your own time is worth.
StoreAgent charges, and here are the plans, all billed monthly:
| Plan | Price | AI chat replies | Memory items | AI tasks |
|---|---|---|---|---|
| Lite | Free | 50 one-time | 1,000 | 200 one-time |
| Growth | $19/mo | 500 | 5,000 | 500 |
| Pro | $49/mo | 5,000 | 25,000 | 2,500 |
| Business | $249/mo | 50,000 | 100,000 | 10,000 |
MCP is included on every plan, the free one included, and no OpenAI or other provider API key is needed on any of them. Lite credits are one-time and don’t renew, so it’s a way to test rather than a way to run a busy store. Every paid plan works on unlimited websites and carries a 14-day money-back guarantee.
Here’s the gotcha you should hear from us rather than discover on your own: MCP calls count as AI tasks, drawn from the same monthly allowance as your content agent runs. That’s fine for the work most people use this for, but an assistant looping through a catalogue can chew through Lite’s 200 one-time credits in a single session. If you’re planning bulk work over MCP, budget it as content work, not as free API access. Our guide to what an AI chatbot actually costs walks through the same arithmetic for chat.
Here’s what the difference looks like in practice (example data, not a real store): a shop owner who wants Claude to write and apply descriptions and tags for 200 thin products, summarise reviews on the top 50, and then keep the chatbot answering shoppers. On core MCP that work isn’t billed, because core MCP can’t do it at all; there are no content abilities, so you’d be writing the copy yourself and using MCP only to push it in. On StoreAgent the same job runs inside a Growth or Pro allowance, and the chatbot, the content agents and the MCP connection all come out of the one plan.
So “free” is accurate and it is also not the whole comparison. Core MCP is free transport. StoreAgent is a priced product that includes transport.
Where WooCommerce Core MCP Is Genuinely Strong
Plenty, and it would be dishonest to pretend otherwise. It’s first-party, so it will always track WooCommerce’s own data model rather than chase it. It’s free and unmetered. Its canonical abilities are carefully specified, with strict input and output schemas, WooCommerce-aware enums, readonly and idempotency annotations, and per-ability permission callbacks checked against WooCommerce’s existing permission model. It can create, update and delete products and move orders through their statuses, which is real write power. Nothing sits between your assistant and your server except a proxy you control, which matters if your policy says no third-party service touches store data. And any plugin can extend it, because it’s the same Abilities API everyone registers into.
It is also where the platform is going. Automattic is building toward agentic commerce on this foundation, and that is good news for every WooCommerce store, including ours. We build on it rather than against it.
Now the honest counterweight, because you should hear it from us rather than find out later. StoreAgent’s own abilities do not create products or change order statuses; that write power comes from WooCommerce’s abilities exposed through the same connection, not from ours. StoreAgent needs a StoreAgent.ai account, and the plugin does nothing on its own. The gateway is a third party in the path, and if your requirement is that nothing leaves your server, core MCP is the honest answer and you should take it. And StoreAgent is not a helpdesk: there’s no human-agent inbox, no SMS and no voice. Escalation sends a conversation summary by email with the shopper set as reply-to, which is a faster human, not a ticketing system.
Where StoreAgent earns its place is everything sitting around the connection. The same plugin runs the storefront chatbot, the AI content generation agents and AI-powered store insights, so MCP is one surface on a product rather than the whole product. If you want to see how that stacks up against other tools, the rest of our StoreAgent comparisons cover it brand by brand.
Frequently Asked Questions
Is WooCommerce’s built-in MCP safe to use on a live store?
WooCommerce’s own documentation says to test thoroughly before deploying to production, warns that future updates may introduce breaking changes, and the launch announcement lists a staging site as the first prerequisite. It works, and developers are using it. But the platform itself is telling you it is a preview, and the earliest endpoint has already been deprecated once.
What can WooCommerce core MCP actually do?
Seven canonical abilities as of WooCommerce 10.9: query, create, update and delete products, query orders, update an order status, and add an order note. There are no abilities for customers, coupons, refunds, shipping, tax, reports or content. Other plugins can add their own abilities through the WordPress Abilities API, and StoreAgent is one of them.
Do I need a Node.js proxy to use StoreAgent’s MCP?
No. StoreAgent runs a standard remote MCP server with OAuth, so you paste the endpoint into your assistant as a custom connector and approve the connection on your own store. There’s no proxy, no Application Password and no JSON config file. Note that Claude needs a Pro, Max, Team or Enterprise plan to add custom connectors, and ChatGPT needs Plus, Pro, Business or Enterprise.
Can I use both StoreAgent and WooCommerce core MCP?
Yes, and plenty of developers will. They’re built on the same WordPress Abilities API, so they’re not mutually exclusive. You can also skip running two connections: WooCommerce’s own abilities can be allowlisted through the StoreAgent gateway, which is how I queried products in testing without touching a proxy.
Does StoreAgent MCP cost anything?
MCP is included on every plan, including the free Lite plan, with no credit card and no API keys. The one thing to watch is that MCP calls count against your AI task allowance, the same pool your content agents draw from, so heavy bulk work over MCP should be budgeted like content work rather than treated as unlimited.
Which Connection Is Right For Your WooCommerce Store?
StoreAgent, if you’re a store owner and you want this working this afternoon. Core MCP, if you’re a developer on a staging site who wants first-party plumbing and no third party in the path. Those are genuinely different buyers, and StoreAgent vs WooCommerce core MCP only looks like a fight if you assume both are aimed at the same one.
Here’s what to do with all this:
- Check the preview label yourself before you plan anything around core MCP, because it moves.
- Count the pieces you have to run, not the features on the page: a proxy, a password and a config file are ongoing work.
- Decide whether you want data access or store work, because seven product and order abilities is a very different offer to content, memory and chat control.
- Budget MCP calls as AI tasks if you’re planning bulk work through an assistant.
- Take core MCP if nothing may leave your server, and don’t let anyone talk you out of that requirement.
If you run a WooCommerce store and want Claude or ChatGPT doing real work on it without becoming a developer first, StoreAgent is built for exactly that. Start free on StoreAgent Lite and connect your assistant before you spend anything.
Sources
- WordPress Developer Resources, Abilities API — Supports: “The WordPress Abilities API landed in WordPress 6.9 as a standard registry of named, permission-checked actions that external systems such as AI agents can discover and run”
- Model Context Protocol, Specification — Supports: “MCP itself is an open standard for connecting AI applications to external tools”
Note: the WooCommerce MCP developer preview status, feature flag, endpoints, authentication requirements, proxy setup and the canonical ability set introduced in WooCommerce 10.9 were verified directly against WooCommerce’s own live developer documentation and release announcements on 2026-09-23. StoreAgent plan pricing, quotas and MCP behaviour were verified against the live StoreAgent pricing and MCP pages the same day. Per the competitor linking policy, WooCommerce documentation pages are named in prose but deliberately not linked.
