Cursor is an AI-native code editor with built-in MCP support. Add Riggr once, authorize in the browser, then use Agent chat to query your live Shopify store and run Riggr Autopilot - same product loop as Claude Code, inside the IDE.
Riggr is a remote MCP server. Cursor does not run a local Riggr process. It connects over HTTPS to https://www.hiriggr.com/api/mcp, discovers Riggr's tools, and lets Agent call them during chat.
| Piece | Role |
| --- | --- |
| Cursor Agent | Plans, writes code, and decides when to call tools |
| Riggr MCP | Read-only Shopify data + project/prompt tools (while you build) |
| Riggr API key .env | Powers the finished Next.js app at runtime (not MCP inside the app) |
First tool call triggers OAuth in your browser. After you approve, Cursor keeps a token (shown in Riggr under AI Tools) and reuses it for later calls.
Add Riggr to your global Cursor MCP config so every project can use it.
Create or edit ~/.cursor/mcp.json (macOS/Linux) or %USERPROFILE%\.cursor\mcp.json (Windows):
{
"mcpServers": {
"riggr": {
"url": "https://www.hiriggr.com/api/mcp"
}
}
}Save the file, then reload Cursor (Cmd+Shift+P / Ctrl+Shift+P → "Developer: Reload Window"), or open Cursor Settings → Tools & MCP and refresh Riggr.
Open Agent chat and ask:
Riggr, what are my last 5 orders?The first tool call opens a browser tab for OAuth. Approve Riggr, return to Cursor, and Agent should answer with real store data.
If that worked, skip to Riggr Autopilot. If not, use the full walkthrough below.
Prefer Riggr in one repo? Put the same JSON in .cursor/mcp.json at the project root instead of ~/.cursor/mcp.json. Project config overrides global when both define riggr.
Open Cursor and sign in. You need a Cursor plan that can use Agent chat with MCP tools. Download from cursor.com if needed.
Sign in at hiriggr.com/login. Your sidebar should say Riggr MCP · Active. If it says Riggr Free, subscribe from /dashboard. MCP tools will not work on the Free tier.
Open your global config:
~/.cursor/mcp.json%USERPROFILE%\.cursor\mcp.jsonOr use the UI: Cursor Settings → Tools & MCP (sometimes labeled Tools & Integrations → MCP) → add a server / edit config.
Paste:
{
"mcpServers": {
"riggr": {
"url": "https://www.hiriggr.com/api/mcp"
}
}
}If the file already has other servers, merge the riggr entry into the existing mcpServers object. Do not wrap two root objects.
No API key or headers block is required here. Riggr authenticates with OAuth on first use (dynamic client registration).
Reload the window, then check Cursor Settings → Tools & MCP. You should see riggr enabled. If it shows an error, open Output → MCP Logs (View → Output, then pick MCP Logs) and fix JSON syntax or the URL.
Correct URL: https://www.hiriggr.com/api/mcp. Common mistake: missing /api.
In a project folder, open Agent (not only inline Tab completion). Ask:
What MCP servers do you have access to?Agent should mention Riggr. If it does not, confirm the server toggle is on, reload again, and make sure you are in Agent chat where MCP tools are available.
Ask Agent to use your store data:
Riggr, list the last 5 orders from my Shopify store.The first tool call triggers OAuth. Here is what happens:
You will see a tool call such as list_orders. Until you authorize, Riggr responds with an OAuth challenge.
A tab opens at hiriggr.com/oauth/authorize. You see the read-only scopes Cursor is requesting and an Authorize button.
Riggr issues an OAuth token (prefix rg_mcp_) to Cursor, valid for one year. The browser tab closes or shows success.
With a token, Cursor fetches real order data from your Shopify store and answers in chat.
The token Riggr issues lives for 12 months. Later Agent sessions and projects reuse it until you revoke the connection in Riggr or the token expires.
By default Agent may ask you to approve each MCP tool call. You can allowlist Riggr tools in Cursor Settings under Agents / Approvals so Autopilot is less interrupt-driven. See Cursor's MCP and permissions docs if you want that tuned.
After OAuth, confirm the token in Riggr:
If Cursor is listed, the connection is real. Later Agent chats on this machine can use the same token.
Once basics work, try something that needs more than one tool:
Riggr, look at my last 20 orders and tell me which SKUs sold the most units.
Agent will call list_orders, often list_products, and reason across both. That is the real value of Riggr in Cursor.
You're set up. Build with Riggr Autopilot - Cursor Agent loads the Spark template over the Riggr MCP bridge and finds your API key on disk. You do not copy/paste the full prompt file.
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 (usually Downloads).
Agent will scaffold the app here. One Spark per folder keeps builds clean (for example ~/Code/riggr-returns).
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 Agent chat. 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 for riggr-*-api-key.env, configure .env.local, and scaffold the Next.js app. Expect 15-30 minutes for a first build. Approve tool calls if Cursor asks.
Details on MCP vs API key live in the Setup guide → Riggr Autopilot.
If something breaks, start with Cursor's MCP Logs (Output panel → MCP Logs), then match the error below.
More generic issues live on the Troubleshooting page.
localhost); you deploy if you want them public.npm install, npm run dev