Bigcommerce Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.2Updated Oct 24, 2026

MCP server for BigCommerce: products, orders. Needs store API credentials.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Lets an assistant work with BigCommerce store data such as products and orders through a local MCP server.

What you can do
This MCP server connects an assistant to a BigCommerce store so it can work with catalog and sales data. The registry description names products and orders as its focus, so expect tools for browsing or managing product listings and order records. It runs locally over stdio rather than as a hosted endpoint.
When to use it
Useful when you manage a BigCommerce store and want an assistant to help with product and order information inside your existing workflow. It is a reasonable fit for store operators or developers who already have BigCommerce API access.
Requirements
Runs as a local process on the user's machine, installed from the npm package @mrfentmen/bigcommerce-mcp over stdio, so Node.js is needed. The description states it needs store API credentials, though no environment variables or headers are declared in the manifest. Desktop only.
Before you install
It requires BigCommerce store API credentials, which grant access to store data; treat them as secrets and scope them as narrowly as the platform allows. Because it covers products and orders, some tools may create, change, or delete store records, so review what each tool does before running it against a live store.

Installation

In SourceWeft

  1. Open Bigcommerce Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.2LatestOct 17, 2026
  2. v1.0.1Sep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.