BigCommerce Connector

Leverage data from BigCommerce to gain insights and drive business decisions

Start for free View documentation

4.8 on G2

Weld · Data Sources

BigCommerceYour warehouseLive

order81 columnsSynced

product67 columnsSynced

order_line_item56 columnsSynced

currency18 columnsSyncing

category17 columnsQueued

Lands in

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

BigCommerce

Data source

Authenticating...

Ready to connect

Overview

BigCommerce in your warehouse.
Ready for your agents.

Leverage data from BigCommerce to gain insights and drive business decisions Weld's BigCommerce connector is fully managed: it extracts data from BigCommerce, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

Agent context

BigCommerce data schema.
The map your agents read.

Every table, field and relationship Weld syncs from BigCommerce is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables: 22
fields: 428
relationships: 8

custom_url_is_customized

boolean

_weld_synced

date

BigCommerce models.
What the numbers mean.

Open-source SQL that turns the raw BigCommerce tables into the reports people ask about. Deploy them in Weld and your agent queries the definitions, not guesses.

Open the models

Weld MCP server

Ask your agent.
It already knows BigCommerce.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the BigCommerce context, finds the tables it needs and queries your warehouse.

Agent contextBigCommerce tables, fields and joins
QuerySQL against your warehouse
OperateCheck, rerun and refresh syncs

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextBigCommercetables22fields428joins8

How many order rows do we have per customer? Use our BigCommerce data.

Reading the BigCommerce context first, so the query uses the right tables and keys.

●weld·search_available_references

⎿raw.bigcommerce.order

raw.bigcommerce.customer

+ 20 more BigCommerce tables

●weld·get_reference_schema

⎿order · 81 columns

joins customer on customer_id

●weld·run_query

⎿select c.id, count(*) from {{raw.bigcommerce.order}} o

join {{raw.bigcommerce.customer}} c on o.customer_id = c.id

group by 1

submitted

●weld·get_query_status

⎿DONE

●weld·get_query_result

⎿rows returned

✓Answered from BigCommerce data in your warehouse

>Ask about your BigCommerce dataMCP

Destinations

Load BigCommerce into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Documentation

BigCommerce setup guide

Step-by-step instructions to configure and start syncing.

MCP server

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

FAQ

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create BigCommerce connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a BigCommerce ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "bigcommerce",
    "destination_schema_name": "bigcommerce_data",
    "sync_interval": "0 * * * *"
  }'
▌