MCP Ecommerce

Installation guide

How to install StackOne BigCommerce MCP

In Claude, ChatGPT, Gemini, Microsoft Copilot, Perplexity, Cursor and Claude Code, with what to check before you start and the first prompts to run.

This is a vendor-hosted server run by StackOne. You don't install the BigCommerce integration locally. Your client connects to a StackOne endpoint, and StackOne handles the BigCommerce authentication and tool execution. The documented config uses `npx` to run the `mcp-remote@latest` bridge. It points at `https://api.stackone.com/mcp?x-account-id=<account_id>` and sends an `Authorization: Basic <YOUR_BASE64_TOKEN>` header. Take the account ID and token from your StackOne account, following the vendor documentation.

Have someone who administers both your StackOne account and the BigCommerce store do the setup, such as a developer or ecommerce operations lead. The server exposes 120 actions, including create, update and delete, so don't use a personal login. Review which actions are enabled for the connected account, and start with read-only prompts. StackOne is a commercial service with its own pricing, and store data passes through its platform.

StackOne BigCommerce MCP setup guide: StackOne's MCP documentation page on stackone.com, shown in a browser frame (store platform MCP server for e-commerce)
StackOne BigCommerce MCP setup guide preview: StackOne’s documentation on stackone.com, captured Oct 13, 2026. The page may have changed since; the link opens the live version.

Before you start

  • A StackOne account with a BigCommerce connection set up. Take the exact steps from the StackOne documentation.
  • Your StackOne <account_id> and a Base64 token for the Authorization: Basic header, from the StackOne dashboard or docs.
  • Node.js installed so npx can run mcp-remote@latest.
  • A decision on which BigCommerce actions the connected account may use. Prefer read-only until the setup is tested.
  • Approval from whoever owns the BigCommerce store and your data policies, since store data flows through a third-party platform.
How it runs
Remote, added by URL
Access
Read and write
Server address
https://api.stackone.com/mcp?x-account-id=<account_id>

StackOne BigCommerce MCP in Claude

  1. Open the Claude Desktop config file. Use the Developer section in Settings to edit it. The docs only show the JSON, not the menu path.
  2. Add the stackone entry under mcpServers, as in the snippet.
  3. Replace <account_id> with your StackOne account ID and <YOUR_BASE64_TOKEN> with your Base64 token.
  4. Save the file and fully restart Claude Desktop.
  5. Check that the stackone server and its BigCommerce tools appear, then run a read-only prompt from the verification list.
claude_desktop_config.json
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

StackOne BigCommerce MCP in ChatGPT

  1. The StackOne docs do not cover ChatGPT, so check the vendor documentation for a supported route first.
  2. In ChatGPT, enable Developer mode and add a custom MCP connector by URL, using the client's standard flow.
  3. The documented endpoint needs an Authorization: Basic header. Confirm that ChatGPT's connector UI can send it, or ask StackOne for an alternative.
  4. If it can, use the URL from the vendor documentation with your own <account_id> and token.
  5. Start with read-only prompts and keep write actions disabled.

StackOne BigCommerce MCP in Gemini

  1. The StackOne docs do not cover Gemini. This uses the standard Gemini CLI mcpServers format with the documented values.
  2. Open the Gemini CLI settings JSON file.
  3. Add the stackone entry under mcpServers, as in the snippet.
  4. Replace <account_id> and <YOUR_BASE64_TOKEN> with your own values.
  5. Restart Gemini CLI, confirm the server is listed, and run a read-only prompt.
Gemini CLI settings (mcpServers)
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

StackOne BigCommerce MCP in Microsoft Copilot

  1. The docs list VS Code as a supported client but give no config for it. They do not cover Copilot Studio.
  2. For GitHub Copilot in VS Code, create or open .vscode/mcp.json in your workspace.
  3. Add the stackone entry under servers, as in the snippet, with your own <account_id> and token.
  4. Save the file, start the server from VS Code's MCP controls, and confirm the tools load in agent mode.
  5. For Copilot Studio, use its custom connector or MCP tool flow. Take the details from the vendor documentation.
.vscode/mcp.json
{
  "servers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

StackOne BigCommerce MCP in Perplexity

  1. The StackOne docs do not cover Perplexity.
  2. In the Perplexity desktop app, open the connectors settings and use its standard way to add a custom MCP server.
  3. The documented setup runs npx with mcp-remote@latest and an Authorization: Basic header. Check that the app supports this, and look in the vendor documentation for any other route.
  4. If it does, enter the command and arguments from the Claude Desktop snippet with your own account ID and token.
  5. Test with a read-only prompt before you allow any write actions.

StackOne BigCommerce MCP in Cursor

  1. Open Cursor's MCP settings, or edit the MCP config JSON file.
  2. Add the stackone entry under mcpServers, as in the snippet.
  3. Replace <account_id> and <YOUR_BASE64_TOKEN> with your own values.
  4. Save the file and reload Cursor if the server doesn't start.
  5. Confirm the BigCommerce tools are listed, then run a read-only prompt.
Cursor MCP config (mcpServers)
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

StackOne BigCommerce MCP in Claude Code

  1. Open a terminal in the project where you want the server.
  2. Run the claude mcp add command from the snippet. It uses the documented npx and mcp-remote@latest arguments.
  3. Replace <account_id> and <YOUR_BASE64_TOKEN> with your own values.
  4. Run claude mcp list to confirm stackone is registered.
  5. Start claude and run a read-only prompt from the verification list.
Terminal
claude mcp add stackone -- npx -y mcp-remote@latest "https://api.stackone.com/mcp?x-account-id=<account_id>" --header "Authorization: Basic <YOUR_BASE64_TOKEN>"

Check that it works

Start with questions that only read data. If these answer from your real account, the connection is good.

  • Get the store information for my BigCommerce store: name, currency settings and configuration.
  • List the first 10 products in the catalog with their IDs and names. Don't change anything.
  • Show all available order statuses, then list the 5 most recent orders. Read only.

Troubleshooting

+The client doesn't list the stackone server or its tools. What should I check?

Check that the JSON is valid and the entry sits under `mcpServers` (or `servers` in `.vscode/mcp.json`). Confirm Node.js and `npx` are on the PATH, then fully restart the client. Run the `npx` command in a terminal to see any `mcp-remote` error output.

+I get an authorization error or a 401 response. What's wrong?

Check that `<account_id>` matches your StackOne account and that the Base64 token is complete, with no stray spaces. The header must read `Authorization: Basic <token>`. Confirm the BigCommerce connection is active in StackOne. Take the exact way to create the token from the vendor documentation.

+Some BigCommerce actions are missing, or writes fail. Why?

The tools you see depend on how the StackOne account and the BigCommerce connection are configured. Check which actions are enabled in StackOne, and whether the BigCommerce API permissions allow them. StackOne's docs say you can limit the actions an agent can use. Take the exact steps from the vendor documentation.

Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.