Orders, products and the store's own sales figures, from your own server.
Your orders live in WooCommerce. What you spent to win them lives in your ad accounts. One question, both answers.
https://mcp.heymetra.com/mcp
How many orders did the store take this week?
Which products sold most last month?
Which products are out of stock or still unpublished?
How do net sales this month compare with last month?
No dashboard, no export, no query language. You ask in the assistant you already use and the answer comes back with the account it came from.
1. Open the REST API screen in WordPress
Sign in to the store's WordPress admin and go to WooCommerce → Settings → Advanced → REST API. The screen lists the keys the store has already issued, and has an Add key button.
It is under WooCommerce, not under the WordPress Settings menu. WordPress has an unrelated Settings of its own, and there is no REST API tab in it.
2. Add a key, and choose what it may do
Choose Add key, give it a description you will recognise later, and pick a user who can see orders. Then set Permissions: Read if this assistant should only answer questions, or Read/Write if you also want it to propose changes to products, prices and orders. Then Generate API key.
The choice is yours and WooCommerce enforces it: with a Read key the store itself refuses any change, so nothing can be edited even by mistake. A Read/Write key lets the store accept changes, and HeyMetra still shows you every change as a card and does nothing until you approve it. HeyMetra cannot see which you picked, which is why it asks you separately on this screen.
Either way the key inherits the chosen user's rights, so a user who cannot see orders produces a key that cannot either.
3. Copy the consumer key and the consumer secret
Both appear once, on the screen that follows Generate. The consumer key starts with ck_ and the secret with cs_, so they cannot be confused with one another.
Leaving that screen loses the secret for good. WordPress does not show it again, and the only remedy is to revoke the key and issue another.
4. Paste the secret into HeyMetra
Choose WooCommerce on the Connections screen and paste the consumer secret. It is stored encrypted and never shown again, here or anywhere else.
5. Enter the store address exactly as the store answers
https:// and the host, nothing after it. If the store answers at www.yourstore.com, type the www.; if it answers without it, leave it out. Saving checks the address and the key against the store immediately.
HeyMetra does not follow a redirect from the address you give it, because that would let a store send it somewhere nobody checked. So the wrong half of a www. pair fails rather than quietly working.
6. Add HeyMetra to the assistant you use
Claude, ChatGPT, Cursor or Codex. HeyMetra gives you the address and the key to paste, and your store answers in that assistant once it connects.
Add HeyMetra once and it is there in every conversation. The address is the same everywhere:
https://mcp.heymetra.com/mcp
npx add-mcp https://mcp.heymetra.com/mcpadd-mcp is a third-party installer that writes the configuration for Claude Code, Codex, Cursor, Antigravity, VS Code and seventeen other agents. It infers the name from the address, so the server lands as heymetra. Run against this endpoint before it was written here.
Claude — Settings → Customize → Connectors → Add custom connector
Paste the address above into Settings → Customize → Connectors → Add custom connector.
On Team and Enterprise plans only an owner can add it, under Organization settings.
Full walkthrough: heymetra.com/mcp/claude/
ChatGPT — Settings → Security and login → Developer mode, then chatgpt.com/plugins
Paste the address above into Settings → Security and login → Developer mode, then chatgpt.com/plugins.
The address has to end in /mcp here.
Full walkthrough: heymetra.com/mcp/chatgpt/
Grok — grok.com/connectors → New Connector → Custom
Paste the address above into grok.com/connectors → New Connector → Custom.
XAI calls this “bring your own MCP”.
Full walkthrough: heymetra.com/mcp/grok/
Perplexity — Settings → Connectors → Custom connector → Remote
Paste the address above into Settings → Connectors → Custom connector → Remote.
Perplexity documents it as a Pro, Max and Enterprise feature.
Full walkthrough: heymetra.com/mcp/perplexity/
Claude Code — claude mcp add --transport http
claude mcp add --transport http heymetra https://mcp.heymetra.com/mcpOr a .mcp.json in the project root; /mcp inside a session shows what connected.
Full walkthrough: heymetra.com/mcp/claude-code/
Codex — ~/.codex/config.toml
[mcp_servers.heymetra]
url = "https://mcp.heymetra.com/mcp"Under an [mcp_servers.] section, then codex mcp login.
Full walkthrough: heymetra.com/mcp/codex/
Cursor — ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
"mcpServers": {
"heymetra": { "url": "https://mcp.heymetra.com/mcp" }
}
}Leave the static OAuth fields empty; HeyMetra does not need them.
Full walkthrough: heymetra.com/mcp/cursor/
Antigravity — ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json in a project
{
"mcpServers": {
"heymetra": { "serverUrl": "https://mcp.heymetra.com/mcp" }
}
}The key is serverUrl, not url, unlike every other JSON client.
Full walkthrough: heymetra.com/mcp/antigravity/
Propose a change to this account. Nothing is sent until you approve it, and HeyMetra cannot undo it afterwards.
Permissions are switched on per connection, and one you leave off is a tool your assistant never sees.
| Permission | What it covers | Changes anything? |
|---|---|---|
| Full account access | Lets your assistant read anything in this account to answer your questions. The figures are the provider's own, not ones HeyMetra has checked. It can also propose changes: none is applied until you approve it, and HeyMetra cannot undo one afterwards — WooCommerce's sales report reads the older order tables, so a store on the newer storage (HPOS) with compatibility mode off reports nothing sold however much it sold. Measured on a live store with 297 orders in it, every figure in that report came back zero. Your assistant checks it against the orders and adds them up rather than repeat the zero, and says when it has, because that arithmetic is its own rather than the store's.. | Yes — every change waits for your approval |
What each permission lets an assistant do, in full
- Ask anything about this account and get the answer from its live data. Reads only, and the figures are the provider's own rather than ones HeyMetra has checked.
- Propose a change to this account. Nothing is sent until you approve it, and HeyMetra cannot undo it afterwards.
Anything that would change something comes back as a proposal you approve, inside bounds that live in code rather than in a prompt: ±50% on a budget, 5 campaigns per action and 20 changes a rolling day, and an approval that expires after 30 minutes. How that works.
Saving fails and the answer says the store redirected the request.
Why: The address on the connection is one the store redirects away from, almost always because of a www. that belongs or one that does not. Measured on a live store: the www. form answers 301 and names the address that works.
Fix: The message names the address the store redirected to. Put that one on the connection, without the path, and save again.
Saving fails with a login error and both values were copied carefully.
Why: WooCommerce answers a wrong key and a missing key with the same error, so its own message cannot tell you which half is at fault. The usual cause is the secret: it is shown once, and a copy that caught a trailing space or missed a character looks right.
Fix: Revoke the key on the REST API screen and issue a new one, copying both values in one sitting. Nothing was stored, so there is nothing to undo.
Saving fails and the store's own /wp-json address opens a 404 page in a browser.
Why: WordPress permalinks are set to Plain. The REST API is reachable at a query-string address in that mode, which is not the address any client uses.
Fix: In WordPress, Settings → Permalinks, choose anything other than Plain and save. The setting affects the whole site, so check the store's pages still open as expected.
The connection saves, and an assistant reports no orders for a period you know you sold in.
Why: The period genuinely holds none. Unlike a marketplace, WooCommerce keeps the store's whole history, so an empty answer here is the store's answer rather than a retention limit.
Fix: Ask about a wider period. If the store's own Orders screen shows rows in the same dates, check the key's user can see orders. A key made for a customer account reads none.
The sales report answers zero for a period the store plainly sold in, and your assistant adds the orders up instead and says so.
Why: The store keeps orders in WooCommerce's newer storage (HPOS) with compatibility mode off. The sales report reads the older tables, which nothing writes to any more, so it reports nothing sold. Measured on a live 9.4.5 store, for a whole year it had sold in.
Fix: Turn on WooCommerce → Settings → Advanced → Features → compatibility mode. It fills the old tables from the new ones from that point on, so figures from before it was turned on stay missing there. That is worth knowing before you compare two periods across that date.
Until then your assistant can still answer about revenue, by adding up the orders themselves; it will say that it did. What it must not do is repeat the report's zero, and if you are ever shown a flat zero for a period you know you sold in, this is the reason.
The connection worked and now every question fails to reach the store.
Why: A security plugin or the host's firewall is blocking /wp-json, which several of them do by default after an update.
Fix: Allow /wp-json in the plugin's settings, or allow HeyMetra's address. Opening the store's /wp-json in a browser shows whether the block is there rather than in the credential.
Connect with a REST key, then ask about the store from your assistant: orders for a period with status, items and totals; products with names, SKUs, prices, stock and whether each is published; and WooCommerce's own sales report, with gross and net sales, orders, items and refunds as the store computes them. One thing is worth knowing before you connect: on stores that use WooCommerce's newer order storage, that sales report can show nothing sold however much the store sold. Your assistant checks the report against the orders, adds them up itself rather than repeat a zero, and tells you when it has. When you connect, you choose whether your assistant may also propose changes, and every change it proposes waits for your approval.
About WooCommerce
WooCommerce is the open-source store that runs on your own WordPress site: products, orders, customers, and checkout. Because it is self-hosted, your sales data stays on your server rather than a vendor's.
The reason to read WooCommerce through HeyMetra rather than through a server that only knows WooCommerce is everything else it can answer in the same breath:
Ads — Google Ads · Meta
Analytics — Google Analytics 4 · Google Search Console · PostHog
Ecommerce — Shopify · Trendyol · WooCommerce
Revenue & CRM — Stripe · HubSpot · Zoho CRM · Zoho SalesIQ · Zoho Marketing Automation
Mobile — AppsFlyer · RevenueCat · Adapty · App Store Connect
Work — Google Calendar · Google Meet · Jira
The full catalogue is at heymetra.com/connectors/.
- WooCommerce connector page
- HeyMetra — what the product is
- Setup for every assistant
- Security and limits
- Pricing
- HeyMetra's own repository
Built by Zeisoft, who make HeyMetra. Not affiliated with WooCommerce. This README is generated from HeyMetra's live connector catalogue and refreshed daily; corrections are welcome as issues.