Bigcommerce MCP connector

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.

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.

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.

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.

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.

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.

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.

Yes. Bigcommerce is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Yes. Both let Claude, ChatGPT or Cursor use Bigcommerce. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Bigcommerce call.

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Bigcommerce: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.