Get store alerts where you already work.
Configure Store MCP destinations for approval requests and supported order events. Store-health notices go to the owner by email only. Shopify order lifecycle events arrive through app webhooks; eBay, Square and WooCommerce do not deliver order events.
eBay, Square and WooCommerce do not provide order-event alerts. Shopify order events arrive through app webhooks; approval and reconnection notices are available on every channel.
How it works
- Choose a plan that includes your destination type and open Notifications in Store MCP. Email starts on Starter; Slack, Discord and webhooks start on Pro.
- Add a Slack, Discord, email or signed HTTPS webhook destination in the browser.
- Select supported events and optionally a store. Do not select an unsupported event expecting polling to fill the gap.
- Send a test, check the destination and review failures in Store MCP. A marked test confirms that destination delivery works, not that every provider webhook has been verified live.
What you can ask
Name the store and review proposed changes. Examples do not create automatic workflows.
Which order events are supported for each of my stores?Which notifications are actually supported for my stores?Show my notification destinations and which ones need attention.Send a marked test to this existing notification destination.Supported work and its limits
Order events by channel
eBay, Square and WooCommerce order-event ingestion is not implemented. There is no polling fallback and no claim of automatic new-order alerts for those channels.
Service notices
Approval-request notifications and owner reconnection emails are separate from provider order events. Test the exact destination before relying on it.
Delivery limits
Notification delivery can be delayed, retried or duplicated; it is not guaranteed exactly once or instantly. Destination failures remain visible in Store MCP.
Scroll the table horizontally to compare every column.
| Event | Shopify | Square | WooCommerce |
|---|---|---|---|
| Created | Supported | Not supported | Not supported |
| Paid | Supported | Not supported | Not supported |
| Canceled | Supported | Not supported | Not supported |
| Shipped | Supported | Not supported | Not supported |
| Delivered | Supported | Not supported | Not supported |
Check the source of each notification
eBay, Square and WooCommerce have no incoming order-event ingestion. Approval notices, owner operational email and marked destination tests are different from commerce events. Shopify and Etsy event integrations have separate deployment and public-access gates. Check event coverage.
Questions before you connect?
Can I create notification destinations by asking my AI?
The AI can explain setup, list existing destinations and send a marked test. Destination creation and secret configuration happen in the Store MCP website.
Do alerts contain buyer details?
Order events carry identifiers and timestamps, not buyer details or raw provider payloads. Your AI can request permitted order details separately under the store’s normal permissions.
Are store reconnection notices sent to every destination?
No. Reauthorization notices are owner emails. Order-event subscriptions and approval-request notifications are separate mechanisms; do not assume every notice is broadcast to Slack or Discord.
Put your store data to work.
Start with the access you choose.