Claude.ai is the browser path for chat with live Shopify data - no Desktop app, no terminal. You add Riggr as a custom remote connector, explore your store and starter prompts over MCP, then hand off the build to Claude Code or Cursor so the Next.js app lands on your computer.
Claude.ai cannot scaffold Sparks or write code on your machine. Building a localhost app requires Claude Code or Cursor. Use Claude.ai for live store Q&A, then hand off Autopilot.
| | Claude.ai | Claude Code / Cursor | | --- | --- | --- | | Job | Chat + reasoning with live store context | Write and run the app on your machine | | How Riggr connects | Remote custom connector (Claude’s cloud calls Riggr) | Local MCP config on your computer | | Filesystem / Autopilot | No access to your Downloads or project folders | Finds API key on disk and scaffolds Next.js | | Best for | Quick ops questions, choosing a prompt, planning | Riggr Autopilot end-to-end |
Same Riggr goal: a working custom app. Claude.ai gets you grounded in real store data. A coding AI finishes the scaffold.
Claude.ai and Claude Desktop both use Anthropic's Connectors UI for remote MCP. Traffic goes from Anthropic's cloud to https://www.hiriggr.com/api/mcp. There is no local JSON config for Riggr on claude.ai.
Sign in at claude.ai. Open Customize → Connectors (from your profile / Customize menu). On Team/Enterprise, an Owner may need to add the connector under Organization settings first; then you Connect as a member.
Click + → Add custom connector (Team Owners: Add → Custom → Web).
Name it Riggr (or similar) and set the URL to:
https://www.hiriggr.com/api/mcpLeave OAuth Client ID / Secret empty unless Riggr support tells you otherwise - Riggr uses dynamic OAuth registration.
Click Add / Connect. Complete Riggr sign-in and Authorize. Read-only Shopify scopes only.
In a new chat, use the + menu → Connectors (or Search and tools) and turn Riggr on for that conversation.
Try:
Riggr, what are my last 5 orders?If that returns live data, skip to What to do before you build. If not, use the full walkthrough below.
Sign in at claude.ai. Custom remote connectors need a plan that allows them. Free is limited to one custom connector - fine if Riggr is that one.
At hiriggr.com/dashboard your account menu should show Riggr MCP · Active. Free tier REST keys are not enough for Claude.ai connectors.
Customize → Connectors → Add custom connector:
https://www.hiriggr.com/api/mcpCommon mistake: https://www.hiriggr.com/mcp (missing /api).
Authorize Riggr in the browser. Then open /connections - you should see a Claude-related MCP client with an active token.
Connectors can be off per chat. Enable Riggr before asking for store data or prompt blueprints.
Riggr, list the last 5 orders from my Shopify store.You should see a tool approval or tool-use indicator (e.g. list_orders). Approve if prompted.
A window opens at hiriggr.com/oauth/authorize. Authorize once. Token lasts about a year unless you revoke it.
Order ids, totals, statuses - from your store, not a generic example.
Riggr tools are read-only on Shopify, but still review approvals. Prefer allowing Riggr tools you trust for the session rather than blind "allow always" on every connector.
Use Claude.ai for work that does not need a project folder:
Examples:
Riggr, summarize fulfillment delays in my last 50 orders.
Riggr, which products show up most in recent returns?Ask Claude to open your Riggr project and pull a starter via MCP (riggr://prompts/... / use_prompt_in_project). Have it explain what the app will do in plain language. You are not pasting a 30KB file - and Claude.ai cannot read files from your Downloads folder.
In the Riggr dashboard, create or open a project and download riggr-*-api-key.env ([Setup guide](/help/setup)). Keep it on your computer for the coding AI - Claude.ai will not pick it up from disk.
When you want a localhost app, switch to Claude Code or Cursor. Claude.ai stays useful for ops questions later.
Follow Claude Code or Cursor until Riggr MCP works there too (you can keep Claude.ai connected for chat).
One app per directory (e.g. ~/Code/riggr-returns).
In Riggr, open the project and copy Talk to your AI, then paste it into Claude Code or Cursor. Or paste:
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.When Autopilot finishes, follow its npm install / npm run dev instructions and open the localhost URL.
More generic issues: Troubleshooting.