BigCommerce MCP server
A maintained MCP server that grounds agents in BigCommerce developer docs: REST and GraphQL APIs, webhooks, OAuth scopes, and code examples.
BigCommerce MCP is a maintained Model Context Protocol server that connects an AI assistant to BigCommerce's developer platform knowledge. Rather than touching a live store, it grounds the model in the BigCommerce APIs so generated integration code is correct: an agent can search across endpoints, webhooks, GraphQL operations, and scopes, then pull the exact request schema, parameters, and OAuth scope requirements for a specific endpoint before it writes a line of code.
The surface mirrors how a BigCommerce developer actually works. It covers REST Management API endpoints by category, the Storefront GraphQL API with query, mutation, and token setup guidance, webhook scope names and payload structures, OAuth scopes with read and write variants, and authentication guides spanning REST tokens, GraphQL auth, and Customer SSO. It can generate runnable code samples, explain rate limits and production client patterns, recommend architecture best practices for pagination, headless, and apps, decode HTTP error codes, and fetch current pages live from developer.bigcommerce.com. It runs locally over stdio via npx with no store credentials required, which makes it safe to add to any project. Alongside the Shopify and WooCommerce servers, it is a clean way to keep an agent accurate while building on BigCommerce.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Available tools
| Tool | Description |
|---|---|
| search_docs | Searches endpoints, webhooks, GraphQL operations, scopes, and best practices across the BigCommerce developer documentation. |
| get_api_endpoints | Retrieves all endpoints for a specified API category. |
| get_endpoint_detail | Fetches the exact request body schema, parameters, and OAuth scope requirements for an endpoint. |
| get_webhook_events | Looks up webhook scope names and payload field structures. |
| get_oauth_scopes | Retrieves OAuth scope names with their read and write variants. |
| get_auth_guide | Answers questions on REST tokens, GraphQL auth, Customer SSO, and OAuth flows. |
| get_graphql_info | Provides GraphQL queries, mutations, and token setup guidance for the Storefront API. |
| get_code_example | Generates runnable code samples for REST, webhooks, OAuth, and GraphQL. |
| get_rate_limit_info | Supplies rate-limit details and production client implementation patterns. |
| get_best_practices | Recommends architecture patterns for pagination, webhooks, apps, and headless setups. |
| get_error_codes | Explains HTTP error codes (400, 401, 403, 404, 422, 429, 500) and their resolutions. |
| fetch_live_doc | Retrieves current documentation pages directly from developer.bigcommerce.com. |
What you can do with it
Write a correct BigCommerce API integration
Before coding against an endpoint, the agent calls get_endpoint_detail to get the exact request schema and required OAuth scopes, then generates client code that matches the real contract.
Wire up webhooks and auth the right way
Using get_webhook_events and get_auth_guide, the agent looks up the correct webhook scopes and payload shape and the proper token flow before building a headless storefront or app.
FAQ
- Is it free?
- Yes. It is free and open source under the MIT license, published on npm as @erplinker/bigcommerce-mcp, and needs no BigCommerce account or store credentials because it serves developer documentation.
- Does it support remote/OAuth?
- No. It runs locally over stdio via npx -y @erplinker/bigcommerce-mcp with no authentication, since it grounds the agent in BigCommerce's public developer docs rather than connecting to a store.
- Does it modify my store?
- No. This server is for development: it searches docs, returns endpoint schemas and scopes, and generates code examples. It does not read or write store data such as products or orders.