Bring Online Store
to Claude Desktop
Learn how to connect BigCommerce to Claude Desktop and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the BigCommerce MCP Server?
Connect your BigCommerce store to any AI agent and take full control of your enterprise e-commerce operations and storefront management through natural conversation.
What you can do
- Catalog Orchestration — List and manage your entire product directory programmatically, retrieving detailed high-fidelity metadata for items, variants, and stock levels
- Order Lifecycle Management — Monitor real-time transaction history and retrieve detailed order profiles (V2 API), including billing and fulfillment status directly through your agent
- Customer Intelligence — Access your complete directory of shoppers and retrieve high-fidelity profile metadata to maintain perfectly coordinated relationship ecosystems
- Storefront Architecture — Manage product categories and brands programmatically to ensure your digital catalog is perfectly organized and up-to-date
- Infrastructure Monitoring — Access store-level configuration including currency settings, language preferences, and account status for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your Access Token, Store Hash, and Client ID from your BigCommerce dashboard (Settings > API Accounts)
3. Start orchestrating your digital commerce from Claude, Cursor, or any MCP client
No more manual toggling between storefront tabs or digging through complex order tables. Your AI acts as your dedicated store manager and commerce architect.
Who is this for?
- Store Managers — instantly retrieve product summaries and monitor order statuses using natural language commands
- Inventory Coordinators — track stock levels and manage product variants without leaving your creative workspace
- Marketing Leads — automate the analysis of customer purchase patterns and catalog growth through simple AI queries
Built-in capabilities (9)
Get details for a customer
Get details for an order
Get metadata for a product
Get store configuration
List product brands
List product categories
List store customers
List recent store orders
Supports filtering by name or brand. List your BigCommerce products
Why Claude Desktop?
Claude Desktop is the definitive way to connect BigCommerce to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 9 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
BigCommerce in Claude Desktop
BigCommerce and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BigCommerce to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for BigCommerce in Claude Desktop
The BigCommerce MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
BigCommerce for Claude Desktop
Every tool call from Claude Desktop to the BigCommerce MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my BigCommerce API credentials?
Log in to your BigCommerce admin, navigate to Settings > API Accounts, and create a new V2/V3 API account to get your token, hash, and client ID.
Does it support both V2 and V3 APIs?
Yes! The server automatically routes requests to the correct endpoint (V3 for products/customers, V2 for orders) to ensure high-fidelity data access.
Where do I find my Store Hash?
Your store hash is the unique identifier in your BigCommerce API URL (e.g., 'xyz123' in api.bigcommerce.com/stores/xyz123/v3/).
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.