The fastest way to point Claude Code at your live Shopify data. If you already have Claude Code installed and a Riggr MCP subscription, you're two minutes away from your first tool call.
Copy, paste, run. Then start using it.
claude mcp add --transport http --scope user riggr https://www.hiriggr.com/api/mcpThen start Claude Code and ask it something about your store:
claudeThe first tool call opens a browser tab for OAuth. Approve Riggr, tab closes, Claude Code has a token for the next year. That's it.
If that worked, skip to Riggr Autopilot. If not, read the full walkthrough below.
Open a terminal and run claude --version. You should see a version number. If not, install Claude Code from claude.com/product/claude-code.
Sign in at hiriggr.com/login. Your sidebar should say Riggr MCP · Active. If it says Riggr Free, subscribe from /dashboard. MCP tools won't work on the Free tier.
Run this command once from any directory:
claude mcp add --transport http --scope user riggr https://www.hiriggr.com/api/mcp--scope user registers Riggr for every project on your machine. Use --scope project instead if you want it scoped to just the current directory.
Run:
claude mcp listYou should see riggr in the list with URL https://www.hiriggr.com/api/mcp. If not, the add command didn't take, re-run step 3.
From any directory, run claude. Once the session starts, ask Claude to check its available MCP servers:
What MCP servers do you have access to?Claude should mention Riggr. If it doesn't, quit Claude Code and restart, MCP config loads on session start.
With Riggr registered, ask Claude Code to actually do something with your Shopify data:
Riggr, list the last 5 orders from my Shopify store.The first tool call triggers OAuth. Here's what happens:
You'll see Claude announce it's calling list_orders. It hasn't authenticated yet, so Riggr's server tells Claude to open an OAuth URL.
A tab opens at hiriggr.com/oauth/authorize. You'll see the scopes Claude Code is requesting (all read-only) and a big Authorize button.
Riggr issues an OAuth token (prefix rg_mcp_) to Claude Code, valid for one year. Browser tab closes.
Now with a token, it fetches real order data from your Shopify store and prints the answer.
The token Riggr issues lives for 12 months. Every future tool call in Claude Code, even in different projects or after restarts, reuses that same token. No repeated OAuth pop-ups.
After the OAuth flow, go to your Riggr dashboard and confirm the token landed:
If Claude Code shows up in that list, the connection is real and persistent. Every subsequent tool call in any project on your machine will use it.
Once basics work, try something that touches multiple tools:
Riggr, look at my last 20 orders and tell me which SKUs sold the most units.
Claude Code will call list_orders, then likely list_products to enrich SKU details, and reason across both. That's the real value, cross-tool reasoning over your live store.
You're set up. Build with Riggr Autopilot - Claude Code loads the Spark template over the Riggr MCP bridge and finds your API key on disk. You don't copy/paste 30KB prompt text.
Create a project and download its API key .env file from /projects. Full steps are in the Setup guide. Autopilot needs that file on your computer.
Claude Code will scaffold the app here. One Spark per folder keeps builds clean.
Open the project in Riggr. Under Talk to your AI, use the emerald Do this first card — copy the kickoff prompt and paste it into Claude Code. That loads the Spark (or Compose for two Sparks) over MCP. After Add-ons unlock, merge them one at a time from the Sparks list.
If you prefer typing it yourself:
Riggr Autopilot: open my Returns Triage project, load the starter prompt over MCP, find my downloaded Riggr API key .env on this computer, and build the app.It will call Riggr MCP tools to see your project and pull the full Spark template (use_prompt_in_project / riggr://prompts/...), search Downloads for riggr-*-api-key.env, configure .env.local, and scaffold the Next.js app. Expect 15-30 minutes for the first build.
Details on MCP vs API key, and why both are required, live in the Setup guide → Riggr Autopilot.
If something breaks, the error message usually names the problem. Real errors and real fixes:
More generic issues (OAuth failures, timeouts, empty results) live on the Troubleshooting page.
Riggr-specific tips that make the Claude Code experience better:
Being explicit about the boundaries so you don't waste time asking for the wrong things:
localhost:3000. You deploy them yourself if you want them online.npm install, npm run dev