Stuck? We’re here.

Shopify’s official MCP server is the Storefront MCP. It lets shopping agents browse and buy from a store the way a customer would. Riggr is the other side of the counter: it lets a merchant’s own AI clients (Claude, Codex, ChatGPT, Cursor) read operational Admin data for their store (orders, fulfillments, products, locations, shipping, and returns) so they can build ops tools in their AI of choice. Launch is Protected Customer Data Level 1: we do not request customer name, email, phone, or street address. Storefront MCP is buy-side, public, and unauthenticated. Riggr is sell-side, OAuth-authenticated per merchant, and read-only for the scopes your store grants at install.

Full setup snippets are on the Docs page. For MCP, connect via OAuth from your AI client (you’ll get an rg_mcp_* token). Project API keys (rg_live_*) are for the REST API your local apps call at runtime. Download the key .env from a project, not for MCP config.

Nowhere persistent for store payloads. Riggr proxies every request live to Shopify and does not warehouse orders, products, or other Admin API response bodies. See the Privacy Policy for the full breakdown.

Riggr is billed through the Shopify Billing API. You can cancel from Riggr’s settings page, or from your Shopify Admin under Settings → Apps and sales channels → Riggr. Shopify usually confirms the cancellation within a minute and issues a prorated credit for the unused portion of the current billing period. MCP access ends once Shopify confirms; you keep Free tier REST API access.

Uninstall Riggr from your Shopify Admin under Settings → Apps and sales channels. Your store credentials are cleared immediately, and Shopify sends a shop/redact webhook about 48 hours later, at which point we hard-delete the shop’s Riggr account data (keys, projects, support chat, and related records).

Most errors come back with a short reason (no_store_connected, no_active_subscription, rate limit). If you see something unexpected, email us with the error message and we’ll dig in.