BigCommerce MCP integration for AI agents.
Connect AI agents to BigCommerce through 5 structured actions, including get product, create product, and delete product. Review authentication, inputs, work…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BigCommerce integration exposes
The BigCommerce Agent App exposes 5 provider-backed actions for marketing and data work. Its current contract lets an authorized agent retrieve one bigcommerce catalog product by id, create a bigcommerce catalog product from json-friendly fields, and delete a bigcommerce catalog product by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BigCommerce account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BigCommerce capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_productREADRetrieve one BigCommerce catalog product by ID.
INPUTS: productId / include / includeFields / excludeFields
create_productWRITECreate a BigCommerce catalog product from JSON-friendly fields.
INPUTS: name / type / price / sku / weight
delete_productHIGH IMPACTDelete a BigCommerce catalog product by ID.
INPUTS: productId
list_productsREADList BigCommerce catalog products with common filters and pagination.
INPUTS: page / limit / keyword / name / sku
update_productWRITEUpdate provided fields on a BigCommerce catalog product.
INPUTS: productId / name / type / price / sku
INPUT CONTRACTS
Know what the action needs before it runs.
get_product
productIdREQUIRED- The BigCommerce product ID.
includeOPTIONAL- Related product resources to include.
includeFieldsOPTIONAL- Product fields to include in the response.
excludeFieldsOPTIONAL- Product fields to exclude from the response.
create_product
nameREQUIRED- The product name.
typeREQUIRED- The BigCommerce product type.
priceREQUIRED- The product price in the store currency.
skuOPTIONAL- The product SKU.
weightREQUIRED- The product weight.
delete_product
productIdOPTIONAL- The BigCommerce product ID.
list_products
pageOPTIONAL- The product page number to request.
limitOPTIONAL- The maximum number of products to return.
keywordOPTIONAL- Search products by keyword.
nameOPTIONAL- Filter products by name.
skuOPTIONAL- Filter products by SKU.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Product
Retrieve one BigCommerce catalog product by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_productControl Create Product
Create a BigCommerce catalog product from JSON-friendly fields. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_productVerify with List Products
List BigCommerce catalog products with common filters and pagination. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_productsSAFETY BOUNDARY
Operate BigCommerce with explicit limits
- Authorize BigCommerce with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_product` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BigCommerce rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BigCommerce task completed successfully.
CONNECTION MODEL
API key
BigCommerce Store API account access token used with the X-Auth-Token header. Create or view Store API accounts in Settings > Store-level API accounts: https://support.bigcommerce.com/s/article/Store-API-Accounts
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BigCommerce.