> This page is for Developer.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.bigcommerce.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.bigcommerce.com/_mcp/server.

# Storefront MCP

> Connect shopping agents and chat widgets to your BigCommerce storefront through Storefront MCP. Enable the server, connect an AI client, and sync the shopper's session.

Storefront MCP lets AI agents shop your storefront on behalf of a shopper. Agents can search products, manage a cart, and hand off to checkout through natural language, using the same access a shopper has. Each storefront has its own MCP server URL.

This page covers which tools Storefront MCP exposes, how to enable it, and how to connect an AI client.

## Available tools

| Tools                                                             | Available to                                                                                                    |
| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| [Storefront tools](/developer/api-reference/mcp/storefront/tools) | Every session on every store: guests, logged-in customers, and B2B buyers                                       |
| [B2B tools](/developer/api-reference/mcp/storefront/b2b)          | Additional tools on B2B Edition stores, for authenticated Buyer Portal users with the matching buyer permission |

Both are served from the same MCP endpoint. The storefront tools (catalog, cart, and checkout) are the base set, and every session gets them, whether or not the store has B2B Edition. On B2B Edition stores, the B2B tools (shopping lists and quotes) are added on top, gated per tool by the authenticated buyer's permissions. Logged-in customers and B2B buyers both authenticate the same way. See [Connecting with session sync](#connecting-with-session-sync-stencil-storefronts).

The set of tools a session sees can change mid-session when permissions or configuration change. For how agents should handle this, see [Tool Resynchronization](/developer/api-reference/mcp/storefront/tool-resynchronization).

## Prerequisites

* A BigCommerce store with an active storefront
* Node.js version 18 or higher (for `npx mcp-remote`)

## Enable Storefront MCP

You must be a **store owner** to enable Storefront MCP on a store.

#### Open MCP settings

In the BigCommerce control panel, go to **Settings**. Under **API and MCP**, select **MCP**.

![API and MCP section of the Settings page in the BigCommerce control panel, with the MCP option listed](/_fern-files/_img/ae5b4063dfa511b9da2858fb58b5852c5576d2a158d01c332b149029bb9aeb53.webp)

#### Enable Storefront MCP and accept the terms

On the **MCP** page, turn on the **Storefront MCP** toggle. Review and accept the terms of service to enable the MCP server for your store.

After you accept, the page shows who accepted the terms and when.

#### Get your MCP server URL

Under **Select storefront**, choose a storefront to view its **MCP API Endpoint**. Each storefront has its own unique MCP server URL.

Copy the URL and share it with your development team or partner solutions you want to integrate with.

![MCP settings page with Storefront MCP enabled, a storefront selected, and its MCP API Endpoint URL](/_fern-files/_img/17a6634e029701311d582f269ec394af4a767d9dec5f75813340bd899539b599.webp)

## Connect your AI client

Once you've enabled Storefront MCP in the control panel, you have an MCP server URL specific to your storefront. Replace `<YOUR_MCP_SERVER_URL>` in the snippets below with that URL.

The steps below happen in your AI client (Claude Desktop, Claude Code, Cursor, or Warp), not in the BigCommerce control panel. Select the tab for the client you use.

#### Claude Desktop

In **Claude Desktop**, go to **Settings → Developer → Edit Config** and add the following:

**`claude_desktop_config.json`**

```json title="claude_desktop_config.json" showLineNumbers={false}
{
  "mcpServers": {
    "bigcommerce": {
      "command": "npx",
      "args": ["mcp-remote", "<YOUR_MCP_SERVER_URL>"]
    }
  }
}
```

#### Claude Code

In the terminal, from the project you want to connect, run the following **Claude Code** command:

```bash showLineNumbers={false}
claude mcp add --transport http bigcommerce <YOUR_MCP_SERVER_URL>
```

If you want to enable the MCP server for all projects, use the `--scope user` option:

```bash showLineNumbers={false}
claude mcp add --transport http --scope user bigcommerce <YOUR_MCP_SERVER_URL>
```

#### Cursor

In your **Cursor** project, add the following to *`.cursor/mcp.json`*:

**`.cursor/mcp.json`**

```json title=".cursor/mcp.json" showLineNumbers={false}
{
  "mcpServers": {
    "bigcommerce": {
      "type": "streamable-http",
      "url": "<YOUR_MCP_SERVER_URL>"
    }
  }
}
```

#### Warp

In Warp, open **Settings → AI → MCP Servers** and add:

```json showLineNumbers={false}
{
  "mcpServers": {
    "bigcommerce": {
      "command": "npx",
      "args": ["mcp-remote", "<YOUR_MCP_SERVER_URL>"]
    }
  }
}
```

### Connecting with session sync (Stencil storefronts)

If you are building a chat widget on a Stencil storefront and want the agent to operate in the shopper's existing browser session, pass a sync token at initialization. This is the same mechanism for storefront and B2B tools. It links the MCP session to a logged-in customer session or an authenticated B2B buyer session, including the buyer's company and permissions:

```http showLineNumbers={false}
POST /api/mcp
X-Bc-Storefront-Sync-Token: <token-from-generateSessionSyncToken>
```

See [Storefront session sync](/developer/api-reference/mcp/storefront/session-sync) for setup instructions, including how to generate the token from Stencil and how to handle reverse sync when a new cart is created.

> **Note**
>
> After you enable Storefront MCP in the control panel, it can take up to 10 minutes for the server to become fully available.