StoreAgent Vs W7S MCP: The Best WooCommerce MCP Server

If you’re weighing StoreAgent vs W7S MCP, you’ve probably already decided the interesting part. You want Claude or ChatGPT talking to your actual WooCommerce store, not guessing at it from a pasted screenshot. W7S sells a Marketplace extension that switches on WooCommerce’s built-in MCP endpoint and gives you a settings screen to manage it. The product page promises “no proxy to install and no code to write”, and for a public HTTPS store that is broadly true.

What that page doesn’t say is what you’re taking on. The endpoint runs on your store, the credential is a WooCommerce REST API consumer key and secret that you create and hand out, and the streaming connection holds a PHP worker open for the length of a session. You are now running an MCP server, and its uptime, its certificate, its firewall rules and its key rotation are yours.

So StoreAgent vs W7S MCP isn’t a contest between two plugins that do the same job. It’s a choice between a raw pipe you configure and secure yourself, and a managed agent layer that also does the store work. This comparison covers how each connection is built, what each assistant can actually do once it’s connected, what you’d really pay, and where W7S is the better buy.

StoreAgent Vs W7S MCP: The Short Answer

StoreAgent is the better choice for most WooCommerce stores because its MCP server is a managed gateway: there is no endpoint on your site, no API key to create, and MCP is included on the free plan. W7S MCP is the better choice when you want a wide set of WooCommerce and WordPress packs already written for you, running on infrastructure you control, and you’re comfortable owning the security of it.

W7S is a careful, well documented developer tool, and the documentation is better than most things sold on the Marketplace. It just isn’t an AI product. It’s a very good set of pipes, and the model, the storefront experience and the store work are all still your problem.

Does W7S MCP Need API Keys And A Server Of Your Own?

Yes, to both, and the docs are honest about it. W7S enables WooCommerce’s own MCP endpoint at /wp-json/woocommerce/mcp and adds two of its own: a Server-Sent Events connector for Claude in the browser, and an OpenAPI schema URL for Custom GPTs. Every one of those lives on your domain. The plugin’s own FAQ puts it plainly: your store talks directly to the AI client, and nothing passes through the vendor.

That is a real selling point for some stores and a real workload for others. To connect, you create a WooCommerce REST API key with Read, Write or Read/Write permission, attached to a user who holds manage_woocommerce. The consumer key and secret are shown once. The assistant sends them as an X-MCP-API-Key header, or, for browser clients that can’t send headers, you hand out a connector URL with a revocable token in it. That token’s credential is then stored in your database, encrypted with a key derived from your wp-config.php salts.

The prerequisites are where most setups fall over, and the W7S troubleshooting guide is essentially a list of them. The site needs a valid trusted certificate. Your CDN has to allow long-lived connections, because the SSE stream holds an open link and a PHP worker for up to about an hour. Your firewall has to let the ChatGPT-User and Claude-User agents through, which the one-click “block AI bots” setting in Cloudflare and several hosting panels does not. A local development site needs an ngrok tunnel, a Node.js bridge and a filter that disables certificate checking. None of that is the plugin’s fault. It is the cost of self-hosting an endpoint.

StoreAgent’s managed WooCommerce MCP server moves that entire list off your store. The public connection ends at a cloud gateway that handles authentication, scope, rate limiting and logging, then calls your store with the same permission checks WP Admin uses. Your store runs no MCP server and opens no new endpoint. You paste one URL into Claude, sign in on your own store’s approval page, and pick read-only or read-write. There is no consumer key, no secret to store, and nothing to rotate.

One thing worth knowing before you buy either: WooCommerce’s own developer documentation still labels the MCP feature a developer preview whose implementation details and integration patterns may change, and lists the /wp-json/woocommerce/mcp path under a “Deprecated WooCommerce MCP Endpoint” heading. W7S registers its own abilities through the WordPress Abilities API as well, so this isn’t a verdict on the plugin. It does mean a self-hosted endpoint is sitting on ground that Automattic is still moving.

What Each Assistant Can Actually Do In Your Store

Take one morning’s worth of real work: “which products are low on stock, write short descriptions for the ones missing them, and refund order 4821 with a note explaining why.” Both tools handle part of that. Neither handles all of it.

W7S wins the first and third. Its always-on WooCommerce Core pack covers listing, searching, creating, updating and deleting products, listing, searching, creating and updating orders, order status and order notes, with no toggle to switch them off. Its gated tool packs then reach customers, coupons, refunds, tax rates, shipping zones, payment gateway settings, webhooks, reports and analytics, transactional emails and system status. A separate group of packs goes past WooCommerce entirely into posts, pages, comments, media, users, post meta, options, site health and installed plugins and themes. If your store runs Subscriptions, Bookings, Memberships, Product Brands or Cost of Goods Sold, matching packs appear on their own. The packs are well built, and the per-pack toggles are the single strongest reason to buy W7S. The ceiling is another matter. StoreAgent’s MCP has no fixed tool list. It exposes any ability registered on the WordPress Abilities API, so WooCommerce core’s own abilities and anything else a plugin on your site registers come through the same gateway once you switch them on.

What W7S cannot do is the middle of that sentence. It has no content generation of its own. “Write short descriptions” means the assistant writes them from whatever it already knows and pushes the text through the product update tool. StoreAgent’s WooCommerce AI abilities include generating product descriptions, tags, alt text, review summaries, coupon descriptions and upsell suggestions as named, permission-checked actions, each one billed and logged, and each one flagged as a write so the assistant has to confirm before it touches the catalogue. The model is included. You register the abilities, allowlist the ones you want per connection, and any ability you’ve allowlisted is callable from the assistant.

I connected Claude to a StoreAgent store and asked it what plan the store was on. It came back with the tier, the included credits and the current usage against them, read straight off the live account, with no key pasted anywhere in the setup. Then I asked for in-stock products and got three back with live SKUs, prices, stock quantities and permalinks. At no point did I open WooCommerce’s REST API screen, generate a consumer secret, or paste anything into the assistant except one URL.

What We’ve Seen: Store owners evaluate an MCP plugin on the tool list and never ask who is responsible when something goes wrong at 2am. A self-hosted endpoint makes you the on-call engineer for a service that AI vendors keep changing under you. The question to ask before you buy isn’t “how many tools does it expose?” It’s “when Claude changes how connectors authenticate, who does the work?”

How StoreAgent And W7S MCP Pricing Compare

This is the least comparable part, because the two products bill for different things. StoreAgent sells monthly plans with a quota that covers the chatbot, the content agents and MCP calls together:

Lite credits are one-time and don’t renew, so it’s a way to test the tool rather than run a busy store on it. MCP access itself is on every plan including Lite. Paid plans run on unlimited websites and carry a 14-day money-back guarantee. The detail that matters here: MCP calls made by a connected assistant draw from the same AI tasks allowance as the content agents, so a chatty agent session costs you credits.

W7S bills like a Marketplace extension, per site and per year:

Nothing meters usage on the W7S side, and that is a genuine advantage. Your assistant can hammer the endpoint all month for the same $39. What the $39 doesn’t include is any AI at all. Claude’s browser connector needs a paid Claude plan (Pro, Max, Team or Enterprise), the ChatGPT route needs a paid ChatGPT plan, and the in-admin Store Control chat needs a third credential, your own Anthropic or OpenAI API key, billed separately by the provider.

Here’s what the difference looks like in practice (example figures, not a real store): a shop on one domain that wants MCP and nothing else pays W7S $39 a year, plus a paid Claude or ChatGPT plan on top, and still has no chatbot and no content generation. The same store on StoreAgent Growth pays $228 a year, needs the same assistant plan for the connector, and gets the storefront chatbot, the content agents and the insights dashboard inside that number. If you want to see how the wider category prices up, we’ve written about what an AI chatbot actually costs.

Beyond The Pipe: What Else Each Tool Does

W7S ships one thing beyond the connection, and it’s a good one. Store Control is a chat window inside WP Admin, opened by a floating button or by typing two slashes in any admin field. It runs the same MCP tools locally, with approval modes that range from asking before every action to auto-approving everyday work but stopping at deletes, refunds and bulk edits. It needs your own provider key to answer, and it caps each tool result at about 12,000 characters so a broad question doesn’t blow up the conversation. For a team member who won’t install a desktop app, it’s the fastest path to using any of this.

Everything else on the StoreAgent side has no W7S equivalent, because W7S never set out to build it. StoreAgent’s WooCommerce AI chatbot runs on the shop front, not in the admin. It reads live product and variation prices at the moment it answers rather than quoting an indexed copy, signed-in shoppers can ask about their own orders, it can offer a coupon to a hesitant shopper, and a competitor blocklist stops it naming brands you’d rather it didn’t. One behaviour caught me out the first time: the widget deliberately holds off appearing on the storefront until the first product index finishes, so a fresh install looks broken for a few minutes when it is working exactly as designed.

Then there’s the work the store needs done rather than asked about. WooCommerce AI content generation covers product and short descriptions, category descriptions, tags, image alt text, review summaries, review moderation, upsell and cross-sell suggestions and product Q&A, runnable on one product, a sample or the whole catalogue from the products list or WP-CLI. AI-powered store insights ties revenue to real WooCommerce orders, maps the funnel from widget impression through to purchase, and files catalogue fixes as suggestions you approve or dismiss. All of it is included on every plan, free included.

Where W7S MCP Is Genuinely Strong

W7S has built a serious piece of software and it would be silly to pretend otherwise. The tool packs are gated at execution time rather than merely hidden from the tool list, so a disabled pack cannot be called even if an assistant knows its name. Read-only enforcement is applied when the tool runs, not by trusting the client. Per-ability toggles let you keep the refund tool while switching off delete-refund. The action log records every call, including the ones that failed and the ones that were denied, with the arguments and the response, and PII redaction is on out of the box so turning logging on to debug doesn’t quietly build a second copy of your customer data. Each person gets their own key and their own revocable connector URL, so revoking one leaves everyone else connected. Support answers in about six hours with no outsourcing, and the documentation reads like someone who has actually supported this.

And the counterweight, because you should hear it from us rather than find it out later. StoreAgent’s own abilities stop at the store and the AI work around it. Everything past that depends on what your site registers, so a plugin that has not adopted the Abilities API gives your assistant nothing to call. W7S wrote its own packs for Subscriptions, Bookings, Memberships, tax rates and shipping zones, and you can use them today. There is no in-admin chat that runs on a model you choose. StoreAgent meters MCP calls against your monthly AI tasks allowance where W7S meters nothing. And StoreAgent’s gateway is a third party in the path by design, which is exactly the thing some stores are trying to avoid.

If your MCP wish list is “refund, reconcile, reconfigure shipping zones and bulk-edit six hundred variations”, W7S does more of that today and $39 a year is a fair price for it. If your wish list is “have an AI that works the store”, the pipe is the easy part. You can see how we line up against the rest of the category in the StoreAgent comparisons.

Frequently Asked Questions

Does W7S MCP work with ChatGPT and Claude?

Yes, both, plus other MCP and OpenAPI clients such as Cursor, Cline, n8n and Ollama. Claude Desktop gets a one-click bundle, Claude.ai in the browser connects over SSE and needs a paid Claude plan, and ChatGPT connects as a Streamable HTTP server. A Custom GPT is the exception: it can import at most 30 tools, and the plugin trims your enabled set to fit.

Do I need WooCommerce API keys to connect an AI assistant?

With W7S, yes. Every connection runs on a WooCommerce REST consumer key and secret attached to a user with manage_woocommerce, and you create, hand out and revoke them yourself. With StoreAgent, no. The gateway uses OAuth, you approve the connection by signing in on your own store, and the token is short-lived and bound to that one store.

Can StoreAgent’s MCP do everything W7S MCP can?

Yes, and in practice it reaches further. StoreAgent’s MCP does not ship a fixed tool list. It exposes any ability registered on the WordPress Abilities API, which means WooCommerce core’s own abilities and anything another plugin on your site registers, alongside StoreAgent’s AI abilities. Read abilities are on by default, and write abilities and anything from other plugins stay off until you allow them. W7S ships a broad set of packs, all of them written by W7S, while StoreAgent’s list comes from whatever your site registers.

How much does StoreAgent cost compared to W7S MCP?

StoreAgent runs $19, $49 or $249 a month with a free Lite tier, billed monthly, and paid plans work on unlimited websites. W7S is $39 a year for a single site, or $62.40 prepaid for two years. W7S is cheaper for the connection alone. It includes no AI, so the model is a separate bill in every case.

Can I try StoreAgent MCP before paying?

Yes. MCP is on every plan including free Lite, so you can connect Claude or ChatGPT to a real store and run read-only calls without paying anything or entering a card. W7S has no free tier, though it carries a 30-day money-back guarantee. WooCommerce’s own MCP endpoint is free but needs manual setup.

Which WooCommerce MCP Setup Is Right For Your Store?

StoreAgent, for most stores, because StoreAgent vs W7S MCP is really a question about who carries the operational load, and the managed answer wins unless you have a specific reason to self-host.

Here’s what to do with all this:

• Decide whether you want an MCP endpoint on your own domain before you compare tool lists
• Write down the five things you’d actually ask an assistant to do and check both tool lists against them
• Add the model to the price, because neither product includes the assistant plan you’ll need
• Ask whether you also want a storefront chatbot and content generation, since only one of these ships them
• Buy W7S if packaged breadth and self-hosting are the requirement, and don’t let us talk you out of it

If you run a WooCommerce store and want an assistant that reads your real catalogue and your real orders without you standing up an endpoint for it, StoreAgent is built for exactly that. Start free on StoreAgent Lite and connect Claude to your store before you spend anything.

Sources

• WooCommerce Developer Documentation, Model Context Protocol (MCP) Integration – Supports: “developer preview whose implementation details and integration patterns may change”
• WooCommerce Developer Documentation, Model Context Protocol (MCP) Integration – Supports: the “Deprecated WooCommerce MCP Endpoint” heading covering /wp-json/woocommerce/mcp

Note: W7S MCP pricing, architecture, authentication, tool packs and logging behaviour were verified directly against the W7S product page and its own WooCommerce.com documentation on 2026-09-23, with the $39 figure confirmed in USD. StoreAgent plan pricing, quotas and MCP behaviour were verified against the live StoreAgent pricing and documentation pages the same day. Per the competitor linking policy, W7S pages are named in prose but deliberately not linked.

Josh Kohlbach CEO

See Full Bio

Ecommerce WordPress WooCommerce Marketing Sales