Bring Online Store
to Cursor
Learn how to connect BigCommerce to Cursor 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 Cursor?
Cursor's Agent mode turns BigCommerce into an in-editor superpower. Ask Cursor to generate code using live data from BigCommerce and it fetches, processes, and writes. all in a single agentic loop. 9 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
BigCommerce in Cursor
BigCommerce and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BigCommerce to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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/).
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.