Cursor AI for ecommerce: run your online store and its theme

In short: Cursor is a code editor with a built-in AI agent. Once you connect it to CloudCart through MCP and a PAT access key, Cursor runs your online store from plain English sentences: prices, stock, product descriptions, reports. In the same window it can also build a custom storefront with Nitrogen. Cursor Premium is $30 a month, and a new CloudCart store is €1 a month for the first 3 months.

What is Cursor (Cursor AI), and what is it used for?

Cursor is a code editor with an AI agent that reads your files, writes code and runs commands on your computer. It is made by Anysphere and built on VS Code, so its menus and shortcuts feel familiar to anyone who has used VS Code. The agent works with the model you choose: from OpenAI, Anthropic (Claude), Google (Gemini), the Grok models or Cursor's own models. It runs as an app for macOS, Windows and Linux, as the Cursor CLI in a terminal, and as cloud agents.

For an online store, Cursor does two jobs. It works with your data (products, prices, stock, orders) through the CloudCart Admin GraphQL API and your PAT token, and with code: a custom storefront with Nitrogen that it writes and previews in the editor, next to the conversation.

This guide is for ecommerce sellers across Europe: what Cursor AI does for a store, what it costs and how to connect it.

How much does Cursor cost? (Cursor pricing)

Cursor has a $0 plan with a limited number of agent requests, and paid plans start at $8 a month. The individual plans on cursor.com/pricing, in US dollars excluding tax:

Cursor plan	Price per month	What it includes	Which store it suits
Entry plan	$0	The agent with a limited number of requests	Trying the connection
Plus	$8	A shared usage allowance, Grok models only	A few tasks a week
Premium	$30	4 times Plus, cloud agents, third-party models at API list price	Daily tasks and storefront work
Super / Ultra	$100 / $200	15 / 50 times Plus	Large catalogs, many long tasks

Two details affect the bill. Your allowance refreshes weekly, so one heavy day does not use up the month. Third-party models (Claude, GPT, Gemini) are billed separately by usage on Premium and above, and you can set a spending cap. Terms change, so check the page before you choose.

Connecting Cursor to CloudCart costs nothing. CloudCart plans, excluding VAT and billed annually, are Baby Pack at €14, Starter Pack at €33, CC Pro at €83 and CC Master at €249 a month, all with 0% commission on your sales. Every feature by plan is on the CloudCart pricing page.

Cursor vs Claude Code vs ChatGPT: which agent for an online store?

Choose Cursor if you want to see the code and files, for example for a custom storefront. Choose Claude Code if you will work only with store data and want the platform reference to update itself. The connection sentence is the same for every agent:

	Cursor	Claude Code	VS Code
What it is	A code editor with a built-in agent	An agent in the terminal or the Claude app	A code editor with an agent chat
CloudCart skills and bulk-change safeguards	Yes	Yes	Yes
Strongest at	Nitrogen storefront and data in one window	Running the store every day	If you already work in VS Code

ChatGPT in the browser answers questions and writes copy, while the Cursor agent works on your computer, with your project files and with your store. Codex, OpenAI's agent, connects with the same sentence but without the plugin skills that guard bulk changes. More: running your store with Claude Code, an online store with ChatGPT and Codex and the VS Code integration page.

How to connect Cursor to your online store, step by step

Connecting takes a few minutes. You need a CloudCart store, owner access (only the owner creates PAT tokens) and a computer with Node.js 20 or newer and git; if they are missing, the agent installs them where it can.

1. Install Cursor and open a folder. Download the app from cursor.com, sign in, then create a folder such as my-store and open it. Your store rules and the files you give the agent live here.
2. Open the agent and paste the sentence:
   Fetch and follow the instructions at https://raw.githubusercontent.com/cloudcart/ai-toolkit/main/prompt.md to set up my AI agent for CloudCart
3. Answer the two questions. The agent asks which language to use and what the connection is for: running the store (the default) or development, such as a Nitrogen storefront.
4. Approve the plugin. Cursor installs the CloudCart plugin with its skills and MCP servers, then the CloudCart CLI.
5. Create an access key. In the admin, open the menu at the bottom left → "PAT Tokens", name the token "Cursor" and choose its permissions. The key starts with cc_pat_ and is shown only once, so copy it straight away.
6. Give Cursor the key and your store address. Write the address without https://, for example mystore.cloudcart.net or your own domain. The agent confirms the connection.
7. Start with a question. "What are my 10 best-selling products for the last month?", then one small change, before you hand it the whole catalog.

To install by hand, choose "Cursor: Install Plugin From URL" in the Command Palette (Cmd/Ctrl+Shift+P) and paste https://github.com/cloudcart/ai-toolkit. The official instructions are public at github.com/cloudcart/ai-toolkit, and you can also copy the sentence from the Cursor integration with CloudCart page.

Write your store rules down once. Cursor reads standing instructions from .mdc files in the project's .cursor/rules folder and from an AGENTS.md file (see the Cursor Rules documentation). Example: "Save new products as drafts only. Prices include VAT. Never touch the Sale category without my confirmation." With a separate store per country, add the language and currency of each.

Cursor MCP: what CloudCart installs in Cursor

MCP (Model Context Protocol) is an open standard that lets AI agents connect to outside systems. An MCP server tells the agent which tools exist and how to call them. Cursor supports MCP servers from plugins and from an mcp.json file: .cursor/mcp.json in the project or ~/.cursor/mcp.json for all projects (see the Cursor MCP documentation). The CloudCart plugin sets them up for you. The connection has four parts:

Part	What it does	Touches store data?
CloudCart CLI	Carries every real read and change, and keeps your sign-in on your computer	Yes, only this part
Dev MCP	Searches the Admin GraphQL API schema and checks every request before it runs	No
Platform reference	A public copy of the CloudCart documentation: how each feature works and where it is set up	No
Storefront MCP	The Storefront API schema for a Nitrogen storefront, added with the development profile	No

The plugin's skills tell Cursor how to work: catalog changes with previews and safeguards, answers from the reference and Nitrogen storefronts. The CloudCart Admin GraphQL API has more than 1,100 operations, from products and stock to orders, customers and discounts, at up to 300 requests a minute.

Your store data in Cursor: metrics, prices, copy

Cursor answers questions about your store from your real orders and products, without opening reports in the admin, and writes ad and email copy from your actual products. Prompts you can paste as they are:

Goal	What you write to Cursor	What you get
Weekly report	"Orders, revenue and average order value this week vs last week?"	The numbers and the change
Stock	"Which products are below 5 units and sell every week? Make a supplier order table."	A purchase order before your busiest week
SEO	"Write an SEO title up to 60 characters and a meta description up to 155 for every product in Bags. Show the first 10."	Titles that say at once what you sell
Ads and email	"Write Facebook ad copy for my 3 best sellers and a newsletter about this month's new products."	Copy built from real names, prices and benefits

Selling in several EU countries? Ask Cursor to compare revenue per store, or to draft German or Italian versions of new product descriptions for you to review. How separate stores per language and currency work is in multilanguage, multicurrency and multistore. More prompts are in 30 prompts for your AI agent.

Which store metrics to track, and how to get them in Cursor

Cursor reads your growth metrics (revenue, orders, average order value, conversion rate, cart abandonment, repeat customers, ROAS) with a read-only PAT token: orders from the CloudCart Admin GraphQL API, and sessions, the funnel and devices from the Analytics reports (the analyticsReport query). Ask, for example, "conversion rate by week for the last 2 months" or "where do we lose the most: cart or checkout?"

Ad spend and product costs are not in the store. Download the report from Meta Ads Manager or Google Ads as a CSV and put it in the project folder, together with a file of your costs: Cursor sees them next to the store data and calculates ROAS and margin by product and by campaign. Formulas and benchmarks are in the 10 KPIs of an online store.

Look at phone and desktop separately. Google indexes a site by its mobile version (Google Search Central), so check it on a phone: the mobile version of your online store.

Marketing with Cursor: emails in Marketing Suite, Meta, Google Ads, TikTok and Search Console

Cursor prepares marketing from real store data: it picks the people and products, writes the copy, creates discount codes and then counts the orders from each campaign. Launching and the budget stay with you.

• Email, SMS, Viber (Marketing Suite): Cursor finds subscribers by what they bought, tags them, creates codes and writes 3 versions of the subject line; you launch in Marketing → Campaigns. See an email campaign in CloudCart.
• Meta, Google Ads and TikTok: Cursor picks the products, writes the copy and calculates real ROAS from UTM orders and the ad export; you run the campaigns. Guides: Meta Ads, Google Ads and TikTok ads.
• Google Search Console: Cursor reads the Performance export, matches queries to products and, with a write key, saves new SEO titles (Search Console for a store).

The store keeps each subscriber's opens, clicks and last activity, so Cursor can tell you who reads your emails and whom to write to less often. Which automated emails to start with: email marketing for an online store.

Why run your store through an AI agent like Cursor?

An AI agent saves hours and speeds up decisions. In a sample cosmetics store with 400 products, manual work drops from 23.1 to 3.8 hours a month, about 19 hours (the calculation is in how much time an AI agent saves).

• A new task without a new workflow. A rules-based automation does only what it was set up for; the agent carries out a task you thought of this morning. See AI agent or rules-based automation.

The bigger gain is speed: the promotion goes live the day you decide on it, and a sold-out product is hidden before it takes an order you cannot fulfil. With 0% commission on sales, those extra orders do not raise your platform bill.

How Cursor makes bulk changes without surprises

Store changes have no general undo button, neither in the admin nor through the API. So the plugin's skills make Cursor follow the same steps: find the products, show what will change, apply it, report back.

• 10 or more products: it shows the count and the first 5 and waits for your "yes". Deleting always asks first.
• 100 or more rows: a script first saves the current values to a CSV file and does a dry run. Over 1,000 rows, that file is never skipped: it is your way back.
• An error on one product: the rest carry on, and the failed ones are listed at the end.

More examples: bulk price and SEO changes with one sentence. Daily backups (Settings → Backup & Restore, a separate subscription) add a second way back.

Your store theme with Cursor: standard theme or Nitrogen storefront

A standard theme is set up in the admin; a fully custom design is built with Nitrogen. Theme template files are not open to merchants, so Cursor cannot edit them, but it can write CSS or JavaScript you paste into Custom CSS/JS (/admin/storefront/custom-assets). Colors, fonts and images you change in the theme editor.

Nitrogen is a storefront in React, React Router, TypeScript and Tailwind CSS, started from the CloudCart starter project (cloudcart/nitro-starter). Every page is your code, while the catalog, orders and payment stay in the admin. It is worth it for what a theme cannot give, such as a product configurator or a comparison tool; for most stores a theme with your logo and colors is enough.

How to build a Nitrogen storefront with Cursor

You create the storefront in the admin, write its code in Cursor with the cloudcart-nitrogen skill, and go live with a push to GitHub or a command.

1. Create the storefront. At /admin/nitrogen click "Create storefront" and choose GitHub or command-line deployment (up to 10 storefronts per store).
2. Run it locally in Cursor. Follow the commands in the Overview tab (cloudcart nitrogen link, env pull), then npm run dev shows the storefront with your real products.
3. Describe the design. "A large photo of the newest collection, three categories below, a reviews block, dark green and sand." The skill reviews design, SEO, security, pixels and a mobile speed score of at least 90 before it deploys, and only when you say so.
4. Deploy and point the domain. A push to the main branch or cloudcart nitrogen deploy publishes it on {handle}.cloudcart.dev; in the Domains tab you point your store domain to it.

Important: the deployment token is shown only once. Cursor tells you when a step is yours and waits.

The starter project keeps your store's URLs, so Google rankings stay. The full walkthrough is in vibe coding an online store with Nitrogen, and more for developers on the developers page.

Is it safe to give Cursor a PAT token?

Yes, if you give it exactly the permissions the task needs. Cursor has no account of its own in your store: it works only within the limits of the key you created.

Access level	What it allows	When to choose it
Read-only (recommended)	Sees everything, changes nothing	Reports, questions, your first days with the agent
Full access	Reads and changes everything	When Cursor manages the catalog and prices
Selected permissions	Only chosen areas: products, orders, customers, stock, discounts, blog, settings, webhooks	When the agent works in only part of the store

• Expiry and IP addresses. Set an end date and up to 20 addresses or networks the key works from.
• Revoking and separate keys. Switch a key off or delete it and access stops at once. Up to 100 keys per store, so give each agent its own and see when each was last used.
• What the model provider sees. Store data Cursor reads is processed under the terms of your Cursor account and model. The GDPR asks you to process only the personal data a task needs (the data minimisation principle in Article 5 of Regulation (EU) 2016/679). If customers' personal data should not pass through the agent, give it a key without "Customers" and "Orders".

What Cursor cannot do for you

• Contracts. The agent sets up shipping and payments in the admin, but you sign the contracts with your couriers and payment provider yourself.
• Product facts. A model can invent a size or an ingredient. Give it the data and check the descriptions, especially for food, cosmetics and children's products.
• Decisions. What you sell, at what price and to whom is up to you.

Already selling on WooCommerce, Shopify, OpenCart or Magento? You do not have to start from zero. The CloudCart team moves your store without stopping sales, and with a 24-month contract migration is €0 until 31 December 2026. Then let Cursor check the imported catalog. Every AI agent CloudCart works with is on the AI integration with CloudCart page.

Create a store for €1 and connect Cursor to it. Send your questions to support@cloudcart.com.

Frequently asked questions