> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/integrations/connect-your-ai-assistant-to-recart-mcp.md). # Connect your AI assistant to Recart (MCP) How to connect Claude, ChatGPT or your coding assistant to Recart so you can ask about your results in plain language. Recart's MCP server lets an AI assistant like Claude, ChatGPT, Codex or Cursor read your Recart data, so you can ask about your opt-in tools, A/B tests, flows, campaigns, subscribers, segments and discounts in plain language instead of clicking through the dashboard. Before you start you'll need admin access to your Recart account to create an API key, and the assistant you want to connect installed and ready. ### **What your assistant can access** The Recart MCP server gives a connected assistant **read-only** access to your account. It can look up: #### Opt-in tools and A/B tests * Your popups, landing pages, embedded forms and SMS keywords, and each one's settings * Opt-in statistics for your popups, landing pages and embedded forms, one at a time or across your whole account: impressions, email and SMS opt-in rates, attributed revenue (also by country and by opt-in segment), new SMS subscribers over time, and popup [bounce rate](/analytics-and-reports/popup-bounce-rate.md) * Popup tags, so you can ask about popups by type. Each popup is tagged with its template (for example opt-in offer or back in stock), opt-in method (for example OneClick or In-Popup Confirmation), trigger (for example exit intent), engagement tool (for example Plinko or Spin the Wheel) and the discount on its success step * Your popup A/B tests: which variant is winning and how each variant compares with the control #### Flows and campaigns * Your automated flows and campaigns, their status and settings, and the segments they're sent to, by name * Performance: revenue and ROI by flow or campaign, which message in a flow drives the most revenue or the most opt-outs, and performance by flow category #### Subscribers and your list * Your SMS list: its size and how it changed by day, week or month, new subscriptions and where they came from, opt-outs by type (keyword, AI, opt-out link, dashboard, public API, integration), list cleaning by reason (deactivated, litigator, landline, reassigned) and subscribers by country * One subscriber at a time, by subscriber ID or phone number: whether they're subscribed and since when, where they signed up, their opt-in and opt-out history, the segments and lists they're in, and their timezone and country #### Segments and lists * Your segments with their status (active, calculating, syncing, unable to sync, dormant), their rules in plain words and, on request, how many SMS subscribers are in each * Your lists (from imports, the dashboard or the API) and their sizes #### Discounts * Your discounts with their status, value and type, including code pools and expiring codes * Find a discount by its code or name, see which code pools are running low, and see which flows, campaigns and popups hand a discount out #### This help center * Your assistant can search help.recart.com to explain how a Recart feature works The assistant cannot create, edit, send or delete anything in Recart. Everything it reads comes from the account tied to the API key you give it, so it only ever sees your own store's data. ### **Step 1: Create an API key** Your assistant signs in to Recart with an API key. 1. In the Recart app, open [**Settings**](https://app.recart.com/settings), then the [**API & MCP**](https://app.recart.com/settings/api) tab 2. In the **API keys** section, click **Create new key** 3. Name the key after the assistant you're connecting, for example "Claude" or "ChatGPT", so you can revoke that one key later without affecting your other integrations 4. Copy the key and keep it somewhere safe — you'll paste it into the assistant in the next step {% hint style="warning" %} Keep the key private. Anyone holding it can read your Recart data. {% endhint %} ### **Step 2: Add Recart to your assistant** Pick the assistant you use below and follow its steps. In every snippet, replace `YOUR_API_KEY` with the key you created in step 1. You'll find the same snippets on the **API & MCP** tab in the app, each with a copy button. #### **Claude Desktop** 1. Install Node.js if you don't have it yet — the connection runs through a small bridge that needs it 2. In Claude Desktop, open **Settings**, then **Developer**, then **Edit Config**. This opens `claude_desktop_config.json` 3. Add the entry below inside `mcpServers`, replace the placeholder with your API key, and save 4. Quit Claude Desktop fully and reopen it. Recart appears under **Developer** once it connects ``` { "mcpServers": { "recart": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.recart.com/mcp", "--header", "X-Recart-API-Key: YOUR_API_KEY" ] } } } ``` The Claude web app only accepts OAuth connectors today, so use Claude Desktop instead. #### **ChatGPT** ChatGPT needs a Business or Enterprise workspace, and a workspace admin has to create the app once before anyone can connect. 1. **Workspace admin, one time:** in ChatGPT, open **Settings**, then **Apps**, then **Create** 2. **Workspace admin:** enter the settings below. ChatGPT asks only for the header name here, not for the key. Accept the notice, create the app and publish it 3. **Each user:** open **Settings**, then **Plugins**, pick **Recart** and click **Connect**. Paste your own API key 4. Until someone has connected, the app shows "No actions are available". That is expected ``` Name: Recart MCP server URL: https://mcp.recart.com/mcp Authentication: Access token / API key Header scheme: Custom Header Header name: X-Recart-API-Key ``` The key is entered when you connect, never in the app settings. #### **Claude Code** 1. Run the command below in your terminal, replacing the placeholder with your API key 2. Start Claude Code and ask it about your Recart data ``` claude mcp add --scope user --transport http recart https://mcp.recart.com/mcp --header "X-Recart-API-Key: YOUR_API_KEY" ``` **Codex** 1. Open `~/.codex/config.toml`, or create it if it doesn't exist 2. Add the block below, replacing the placeholder with your API key, and save 3. Start Codex and ask it about your Recart data ``` [mcp_servers.recart] url = "https://mcp.recart.com/mcp" http_headers = { "X-Recart-API-Key" = "YOUR_API_KEY" } ``` #### **Cursor** 1. Open `~/.cursor/mcp.json`, or .cursor/mcp.json inside a project to limit it to that project. Create the file if it doesn't exist 2. Add the entry below, replacing the placeholder with your API key, and save 3. Cursor picks the server up on its own. If it doesn't, reload the window ``` { "mcpServers": { "recart": { "url": "https://mcp.recart.com/mcp", "headers": { "X-Recart-API-Key": "YOUR_API_KEY" } } } } ``` ### **Step 3: Ask away** Once the assistant is connected, ask it about your store in your own words. For example: * How did my popups perform last month? * Which variant is winning my welcome popup A/B test? * Which campaign drove the most revenue last week, and at what ROI? * Which message in my abandoned cart flow causes the most opt-outs? * How did my SMS list grow this month, and why did people unsubscribe? * Are any of my discount code pools running low? * Which of my popups use Plinko, and how are they doing? If your assistant is connected to more than one store, say which one you mean — by store name or domain — and it will use that account. ### **Good to know** * **The connection is read-only.** Your assistant can look at your data but can't change anything in Recart * **No personal data in answers.** Your assistant never gets subscribers' phone numbers, emails or names. If you look a subscriber up by phone number, the number is only used to find them * **Segment members aren't listed.** Your assistant can tell you how many SMS subscribers are in a segment, but not who they are * **Opt-in statistics cover the last 18 months.** * **Popup tags describe each popup as it is now.** If you switch a popup from Spin the Wheel to Plinko, all its numbers show under Plinko. Only popups have tags — landing pages, embedded forms and keywords don't * **One key per assistant.** Naming each key after the assistant it belongs to means you can revoke a single connection later without breaking your other integrations * **Revoking a key cuts the connection immediately.** Delete the key in the **API keys** section of the **API & MCP** tab, then remove the entry from the assistant's config * **Numbers come straight from Recart.** Opt-in rates count unique sessions rather than subscribers, the same way they do in your dashboard, so an assistant's summary matches what you see in the app If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md) We'd be happy to help! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.recart.com/integrations/connect-your-ai-assistant-to-recart-mcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.