# Bigcommerce MCP connector The Bigcommerce connector lets Claude, ChatGPT, Cursor and the Elaichi Agent look up your Bigcommerce products, orders and customers, so anyone on your team can ask about a store record in plain language and get an answer from the live catalog. Source: https://elaichi.ai/connectors/bigcommerce/ ## Facts | | | | --- | --- | | Application | Bigcommerce | | Category | Ecommerce | | AI tools | 6 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Bigcommerce is connected - Which Bigcommerce orders came in yesterday and their totals? - Show Bigcommerce products in the summer sale catalog. - Summarize this week's new Bigcommerce customers by store. ## Connect Bigcommerce in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Bigcommerce. 2. Optionally set Share with, then press Connect. 3. Paste a Bigcommerce API key. One person generates a token in Bigcommerce and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Bigcommerce tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Bigcommerce to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Bigcommerce to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Bigcommerce to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Bigcommerce to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Bigcommerce tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Bigcommerce through Elaichi ### Find an order while the customer waits Support. Ask for an order by its number and get the items, totals, shipping address and status back in one answer, without opening the Bigcommerce admin. ### Pull up a customer's purchase history Support. Look up a shopper by name or email, see their Bigcommerce customer record and past orders, and answer their question with the facts in front of you. ### Review the orders that came in today Operations. List recent Bigcommerce orders, spot anything awaiting fulfillment or flagged as a problem, and hand the list to whoever packs and ships. ### Check a product's details before a promotion Merchandising. Get a product by its ID to confirm the price, description, variants and stock level before it goes into a campaign or a sale. ### Reconcile a week of store sales Finance. List Bigcommerce orders for a date range, total them up, and compare against what landed in the payment account. ### Build a list of repeat buyers Marketing. List Bigcommerce customers and their orders, then ask the agent to pick out the people who have bought more than once for a loyalty message. ## Frequently asked questions ### How do I connect Bigcommerce to Claude? Connecting Bigcommerce to Claude takes two steps. First, connect Bigcommerce in Elaichi by pasting in your Bigcommerce API key; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the Elaichi endpoint, https://api.elaichi.ai/mcp. Claude then signs you in through Elaichi and your Bigcommerce products, orders and customers are available to ask about. ### Does Bigcommerce work with ChatGPT and Cursor as well as Claude? Yes. Once Bigcommerce is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Bigcommerce once and every client you use picks it up. ### What can an AI agent actually do with my Bigcommerce data? With Bigcommerce connected, an agent can list your products, orders and customers and pull up any one of them by its ID. That means you can ask what is in order 4821, which products are low on stock, what a particular customer has bought, or how many orders came in this week, and get the answer from the live store. This connector reads Bigcommerce records; it does not create, edit or delete them. ### Does connecting Bigcommerce give the AI everything in my store? No. Every call to Bigcommerce runs inside the access of the person who signed in, so the agent sees the products, orders and customers that person's Bigcommerce API key can see and nothing more. Elaichi can narrow that access further with restrictions, for example limiting a team to products only, but it can never widen it beyond what Bigcommerce already allows. ### Can my team share one Bigcommerce connection? Yes. One person connects Bigcommerce in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every lookup of a Bigcommerce order or customer is recorded in the audit log under the name of the person who asked. ### Can I stop an agent from deleting or changing things in Bigcommerce? The Bigcommerce connector only reads products, orders and customers, so an agent cannot delete or change anything in your store through it. Beyond that, restrictions in Elaichi work per action, so you can switch off any lookup you do not want a team to have, such as customer records. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it. ### What happens to a Bigcommerce connection when someone leaves? When you offboard someone in Elaichi, their access to Bigcommerce through every client ends at once. If they were part of a shared Bigcommerce connection, it keeps working for everyone else on the team. If you want to remove Bigcommerce altogether, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time. ## All 6 Bigcommerce tools Every tool below is callable through https://api.elaichi.ai/mcp once Bigcommerce is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Bigcommerce products** (List). Returns a list of Products. You can filter by their names, price, brands, etc. - **Get single Bigcommerce product by ID** (Get). Get a single product by its ID. - **List all Bigcommerce orders** (List). Gets a list of orders using the filter query. The default sort is by order id, from lowest to highest. By default, requests sent without query parameters will only return 50 orders. - **Get single Bigcommerce order by ID** (Get). Get a single Order by its ID. - **List all Bigcommerce customers** (List). Returns a list of Customers. They can be filtered by their names, emails, phones, etc. - **Get single Bigcommerce customer by ID** (Get). Get a single Customer by their ID.