@erplinker/bigcommerce-mcp
Provides tools for interacting with the BigCommerce developer platform, including REST endpoints, webhooks, OAuth scopes, GraphQL APIs, code examples, and best practices for building on BigCommerce.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@erplinker/bigcommerce-mcp search for order webhook payload structure"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@erplinker/bigcommerce-mcp
The complete BigCommerce developer platform as an MCP server — wired into Cursor, Claude, Windsurf, and any MCP-compatible AI tool.
What This Does
Gives your AI assistant the knowledge of a senior BigCommerce Solutions Engineer. Instead of hallucinating API details, your AI calls this MCP server and gets precise, structured answers about every endpoint, webhook, auth pattern, GraphQL operation, OAuth scope, and code example in the BigCommerce developer ecosystem.
Coverage:
22 API categories — 171 fully-documented REST endpoints (v2 + v3)
42 webhook event scopes with payload field reference
21 OAuth scopes with read/write variants
3 GraphQL APIs — 30 operations (Storefront, Admin, Account)
12 MCP tools — search, endpoints, code gen, auth, best practices, live docs
49 live doc routes — fetches directly from developer.bigcommerce.com
Related MCP server: @prosodyai/mcp-docs
Install
# Global install (recommended)
npm install -g @erplinker/bigcommerce-mcp
# Or local project install
npm install @erplinker/bigcommerce-mcpCursor Setup (CLI + MCP Config)
Step 1 — Install globally
npm install -g @erplinker/bigcommerce-mcpFind your binary path (you'll need this):
which bigcommerce-mcp
# macOS/Linux: /usr/local/bin/bigcommerce-mcp
# nvm users: ~/.nvm/versions/node/v20.x.x/bin/bigcommerce-mcp
# Windows: C:\Users\you\AppData\Roaming\npm\bigcommerce-mcp.cmdStep 2 — Add to Cursor MCP config
Open the file at one of these paths:
macOS:
~/.cursor/mcp.jsonWindows:
%APPDATA%\Cursor\mcp.jsonLinux:
~/.config/cursor/mcp.json
Or via Cursor UI: Cmd+Shift+P → "Cursor: Open MCP Settings"
{
"mcpServers": {
"bigcommerce": {
"command": "bigcommerce-mcp",
"args": [],
"description": "BigCommerce full developer docs — REST, GraphQL, Webhooks, Auth, Stencil, Catalyst"
}
}
}Using nvm or non-standard PATH? Use the full absolute path:
{ "mcpServers": { "bigcommerce": { "command": "/Users/you/.nvm/versions/node/v20.18.0/bin/bigcommerce-mcp" } } }
No global install? Use npx:
{ "mcpServers": { "bigcommerce": { "command": "npx", "args": ["-y", "@erplinker/bigcommerce-mcp"] } } }
Step 3 — Restart Cursor and verify
Fully quit and reopen Cursor
Open AI chat → type:
@bigcommerce search for order webhooksYou should see the MCP tool execute and return structured data
If the tool doesn't appear, check View → Output → MCP in Cursor for error logs.
Step 4 — Add the Master System Prompt
This is the key step. It tells Cursor's AI how to use the MCP tools like an expert.
Option A — Global (applies to all Cursor projects):
Cursor → Settings (Cmd+,) → Cursor Settings → Rules → "Rules for AI"Paste the contents of the Master Prompt section at the bottom of this README.
Option B — Per-project .cursorrules (recommended for BC projects):
Create a .cursorrules file in your project root and paste the Master Prompt from the section below.
Option C — New MDC format (Cursor 0.43+):
mkdir -p .cursor/rulesCreate .cursor/rules/bigcommerce.mdc and paste the Master Prompt from the section below.
Claude Desktop Setup
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"bigcommerce": {
"command": "bigcommerce-mcp"
}
}
}Windsurf / Other MCP Clients
{
"mcpServers": {
"bigcommerce": {
"command": "bigcommerce-mcp",
"args": []
}
}
}The 12 MCP Tools
Tool | Use When |
| Any BC question — searches endpoints, webhooks, GraphQL, scopes, best practices |
| Need all endpoints for a category (catalog, orders, customers, cart, etc.) |
| Need exact body schema, params, or OAuth scope for one endpoint |
| Need webhook scope names and payload structures |
| Setting up API accounts or app scopes — never guess these |
| Auth questions: REST, GraphQL tokens, Customer SSO, OAuth app flow |
| GraphQL queries, mutations, token setup |
| Need runnable code: REST calls, webhooks, OAuth, GraphQL, cart/checkout |
| Writing any loop or bulk operation — includes full production client |
| Architecture decisions: pagination, webhooks, apps, headless, performance |
| Debugging API errors (400, 401, 403, 404, 422, 429, 500) |
| Need live docs from developer.bigcommerce.com (49 available topics) |
Example Prompts That Work Great
"What endpoints do I need to build headless cart and checkout?"
"Write a Next.js /auth callback handler for the BigCommerce OAuth flow"
"Give me a production webhook handler for order.created in TypeScript"
"What's the GraphQL query to fetch a product by URL path with prices?"
"How do I sync 200k inventory records without hitting rate limits?"
"What OAuth scopes do I need for managing orders and customers?"
"How do I SSO a customer from my auth system into BigCommerce?"
"Show me how Price Lists work with customer groups — with code"
"I'm getting a 403 on POST /catalog/products — what scope am I missing?"
"Write Stencil JS to AJAX add-to-cart and update the cart counter"
"How do I create a channel and assign products to it in MSF?"
"Generate bulk inventory sync code with rate limit handling"Master Prompt — Paste into Cursor Rules for AI
You are an expert BigCommerce developer. You have access to the BigCommerce Developer
Documentation MCP server (@erplinker/bigcommerce-mcp).
ALWAYS call MCP tools before answering BigCommerce questions. Never answer from
memory alone when a tool will give you precise information.
TOOL USAGE RULES:
- search_docs(query) — Call first for any BC API or feature question
- get_api_endpoints(category) — When user needs to know what endpoints exist
Categories: catalog, orders, customers, cart, checkouts, channels, shipping,
payments, inventory, pricelists, promotions, webhooks, scripts, themes,
settings, pages, subscribers, wishlists, reviews, store-info, tax
- get_endpoint_detail(path_contains, method?) — For exact body/params/scope
- get_code_example(operation, language?) — Before writing any BC API code
Operations: getProduct, getProductsByCategory, createCart, routeQuery,
customerLogin, webhookSetup, oauthApp, rateLimit, inventorySync,
or any "METHOD /path" like "POST /catalog/products"
Languages: node (default), python, php, curl
- get_webhook_events(category?, search?) — For webhook scope strings
Categories: Orders, Products, Cart, Customers, Channels, Inventory, Shipment, Store
- get_oauth_scopes(resource?) — NEVER guess scope names. Always call this.
- get_auth_guide(type) — type: rest | graphql | customer_login | oauth_app | all
- get_graphql_info(api?, operation_search?) — api: storefront | admin | account
- get_rate_limit_info() — Always call when writing loops or bulk operations
- get_best_practices(topic) — topic: general|pagination|webhooks|apps|headless|performance
- get_error_codes(code?) — When user hits an API error, call this first
- fetch_live_doc(topic) — For niche or recently updated features
Topics: quickstart, about-api, authentication, api-accounts, oauth-scopes, catalog,
orders, customers, cart, checkouts, channels, shipping, payments, inventory,
pricelists, promotions, themes, scripts, settings, pages, subscribers, wishlists,
reviews, gift-certificates, graphql-storefront, graphql-admin, graphql-account,
webhooks, webhook-events, app-guide, app-callbacks, embedded-checkout,
customer-login, stencil, stencil-cli, catalyst, headless, storefront-tokens,
dev-portal, app-types, app-installation
ALWAYS IN GENERATED CODE:
- REST Management header: X-Auth-Token: {access_token}
(never use Authorization: Bearer for REST Management)
- GraphQL Storefront header: Authorization: Bearer {channel_token}
- Always include Content-Type: application/json and Accept: application/json
- Always handle 429: read X-Rate-Limit-Time-Reset-Ms, wait, retry
- Never put X-Auth-Token in client-side / browser JavaScript
- Show required OAuth scope in a comment above every API call
- Use ?include= query params to embed nested objects (avoid N+1 requests)
- Use bulk/batch endpoints for multi-record operations
- Use webhooks instead of polling the API
BASE URLS (always use these exactly):
- REST v3: https://api.bigcommerce.com/stores/{store_hash}/v3
- REST v2: https://api.bigcommerce.com/stores/{store_hash}/v2
- GraphQL SF: https://{store_domain}/graphql
- Payments: https://payments.bigcommerce.com/stores/{store_hash}/payments
(NOTE: Payments API is on a DIFFERENT HOST than REST Management)
- OAuth: https://login.bigcommerce.com/oauth2/token
ARCHITECTURE DECISIONS:
- Headless storefront → GraphQL Storefront API + Catalyst (Next.js)
- Store data management → REST Management API v3
- Real-time event handling → Webhooks (never polling)
- Customer SSO / sign-in → Customer Login API (HS256 JWT, 30s TTL)
- App Marketplace app → OAuth app (/auth + /load + /uninstall callbacks)
- Injecting JS to storefront → Scripts API (not manual theme edits)
- Customer-group pricing → Price Lists API
- Automatic cart discounts → Promotions API (not legacy Coupons)
- Multi-location inventory → Inventory v3 API with location_id
- Multi-storefront setup → Channels API + MSF architecture
ERROR HANDLING TEMPLATE (always include):
if (!response.ok) {
const error = await response.json();
throw new Error(`BC API ${response.status}: ${JSON.stringify(error.errors ?? error.title ?? error)}`);
}
RATE LIMIT TEMPLATE (always include for loops):
if (response.status === 429) {
const ms = parseInt(response.headers.get('X-Rate-Limit-Time-Reset-Ms') ?? '5000');
await new Promise(r => setTimeout(r, ms + 200));
// retry request
}
PAGINATION TEMPLATE (REST v3):
let page = 1;
do {
const res = await bc.get(`/endpoint?page=${page}&limit=250`);
// process res.data
page++;
} while (page <= res.meta.pagination.total_pages);Project Structure
bigcommerce-mcp/
├── src/
│ ├── index.ts # MCP server, all 12 tool handlers
│ ├── docs/
│ │ ├── knowledge-base.ts # 171 endpoints, 42 webhooks, 21 scopes, auth
│ │ └── fetcher.ts # Live doc fetcher → developer.bigcommerce.com
│ └── utils/
│ └── code-generator.ts # Code example generators (REST, GraphQL, OAuth)
├── dist/ # Compiled output (ships with npm package)
├── claude_desktop_config.example.json
├── package.json
├── tsconfig.json
├── LICENSE
└── README.mdLinks
License
MIT — see LICENSE
Available Tools
12 toolsfetch_live_docA
Fetch a live documentation page from developer.bigcommerce.com. Use when you need the most up-to-date documentation for a specific topic not covered by the other tools.
Inputs: topic (required).
get_api_endpointsA
Get all REST API endpoints for a specific BigCommerce API category. Returns methods, paths, descriptions, required OAuth scopes, and parameter info.
Inputs: category (required), method.
get_auth_guideA
Get authentication guides and code examples for BigCommerce APIs — REST Management auth, Storefront GraphQL tokens, Customer Login API (SSO), and the OAuth app installation flow.
Inputs: type (required).
get_best_practicesA
Get best practices for BigCommerce development by topic area — pagination, webhooks, app development, headless/Catalyst, performance, and general API usage.
Inputs: topic (required).
get_code_exampleA
Get ready-to-use code examples for BigCommerce API operations in multiple languages. Includes REST API calls, GraphQL queries, webhook handlers, OAuth flow, cart/checkout, customer login, and more.
Inputs: operation (required), language.
get_endpoint_detailA
Get comprehensive detail for a specific BigCommerce API endpoint — request body schema, path parameters, query params, example response, OAuth scope, and usage notes.
Inputs: path_contains (required), method, category.
get_error_codesA
Get HTTP error code reference for BigCommerce APIs with explanations and troubleshooting guidance.
Inputs: code.
get_graphql_infoA
Get information about BigCommerce GraphQL APIs — Storefront API, Admin API, and Account API. Includes available operations, auth methods, and endpoints.
Inputs: api, operation_search.
get_oauth_scopesA
Get the complete OAuth scope reference for BigCommerce. Find the correct read/write scopes for any API resource.
Inputs: resource.
get_rate_limit_infoA
Get BigCommerce API rate limit details — how the bucket algorithm works, response headers, and a production-grade client with auto-retry and pagination.
Inputs: include_client_code.
get_webhook_eventsA
Get all BigCommerce webhook event scopes with descriptions and payload structures. Filter by category or search by name.
Inputs: search, category.
search_docsA
Full-text search across all BigCommerce developer documentation — API endpoints, webhooks, authentication, GraphQL, Stencil, Catalyst, best practices, and more. Use this as the first tool when you're not sure where to start.
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose, ranging from fetching specific documentation pages to providing detailed endpoint info, error codes, and search. No two tools overlap in functionality.
Most tools follow a 'get_' prefix pattern, but 'fetch_live_doc' and 'search_docs' deviate. Otherwise, all names use lowercase snake_case and verb_noun structure, making them predictable.
With 12 tools, the server is well-scoped for a documentation-focused MCP. Each tool covers a specific aspect of BigCommerce developer resources without being excessive or too sparse.
The set covers major documentation areas (API endpoints, auth, best practices, code examples, GraphQL, OAuth, rate limits, webhooks, and search). While a few niche topics might be missing, search_docs provides a fallback.
Maintenance
Related MCP Connectors
Discover, plan and run tools across your connected business systems through one OAuth MCP endpoint
Email inboxes, webhook URLs, mock APIs and 170+ tools for coding agents over one MCP connection.
100+ MCP tools for AI agents: content metadata, trade intelligence, business-expertise analysis.
327 dev tools via REST API and MCP. Generate Dockerfiles, schemas, K8s, APIs, and more.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with BigCommerce stores through comprehensive REST API integration. Provides tools for managing products, customers, and orders with advanced filtering and relationship tracking capabilities.35MIT

@prosodyai/mcp-docsofficial
AlicenseAqualityBmaintenanceExposes ProsodyAI documentation, SDK references, REST API reference (OpenAPI), and curated implementation recipes to AI coding agents via MCP tools and resources.8MIT- FlicenseNot gradedqualityDmaintenanceGive your AI agents instant access to Keboola API documentation. Search endpoints, get parameter details, and generate curl examples—all through MCP tools.-
- AlicenseAqualityDmaintenanceProvides comprehensive documentation for MAX Platform, including Bot API endpoints, guides, Bridge API, and UI components, via MCP tools and resources for AI coding agents.8MIT