Ecommerce
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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
6 tools
How to connect
How to connect Bigcommerce to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Bigcommerce once
-
Open Connections, choose Add connection, and pick Bigcommerce.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Bigcommerce to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Bigcommerce to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Bigcommerce through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Find an order while the customer waits
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.
-
Support
Pull up a customer's purchase history
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.
-
Operations
Review the orders that came in today
List recent Bigcommerce orders, spot anything awaiting fulfillment or flagged as a problem, and hand the list to whoever packs and ships.
-
Merchandising
Check a product's details before a promotion
Get a product by its ID to confirm the price, description, variants and stock level before it goes into a campaign or a sale.
-
Finance
Reconcile a week of store sales
List Bigcommerce orders for a date range, total them up, and compare against what landed in the payment account.
-
Marketing
Build a list of repeat buyers
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.
Try asking
- “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.”
AI tools
Bigcommerce tools for your AI agents
6 tools are ready to call through Elaichi's MCP endpoint the moment you connect Bigcommerce, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Bigcommerce gets you
6 screens from the product, each doing one job for your Bigcommerce account.
The agent
Ask about Bigcommerce orders in plain language.
Questions about products, orders and customers get answered from live Bigcommerce records.
- products
- orders
- customers
- order line items
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Bigcommerce here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
6 Bigcommerce tools ready without custom code.
Product, order and customer resources with list and get methods, cataloged and callable.
- List all Bigcommerce products
- Get single Bigcommerce product by ID
- List all Bigcommerce orders
- Get single Bigcommerce order by ID
ElaichiToolsToolboxes
Every team gets its own Bigcommerce toolbox.
Merchandising, support and finance each see the Bigcommerce toolbox scoped to their work.
- Merchandising
- Customer support
- Finance
- Marketing
ElaichiToolboxesShared connections
Share a Bigcommerce store, never the credential.
See who connected each store and which teams and members work through it.
- Retail US
- Retail EMEA
- Wholesale
- Support
ElaichiConnectionsAudit log
Every Bigcommerce call is written down.
When, who, what happened, type and resource, appended for each order and product read.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Bigcommerce orders into a digest.
Six steps fetch orders, group them, draft a digest, wait for approval, post back.
Bigcommerce digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch products
Bigcommerce
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Bigcommerce
Queued
Collections and dashboards
Bigcommerce health computed on a schedule.
Four metrics, 14 days of records created and a breakdown by team, no model involved.
Bigcommerce health
Refreshed 4 minutes ago · every 15 minutes · from the products collection
Products
1,284 ↓ 12%
Orders
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Products created
Last 14 days
By team
Share of activity
Retail US 34%
Retail EMEA 27%
Wholesale 21%
Support 18%
Related connectors
More from the catalog
FAQ
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 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.
Put Bigcommerce in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.