Skip to main content
Glama
isaacgounton

BigCommerce API MCP Server

by isaacgounton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to BigCommerce API MCP Server

No user-submitted related servers found.

    Related Servers

    • BareMCP

      barecommerce-core
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage BareCommerceCore e-commerce stores through 46 tools covering products, orders, customers, categories, pages, media, webhooks, and analytics. Uses secure OAuth authentication without requiring API keys in chat.
      7 npm
      MIT

    • ecommerce-mcp

      bookknhp
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI to view and manage e-commerce data such as products, orders, and coupons, and perform actions like updating prices, stock, and generating sales reports.
      -

    • mcp-woocommerce

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with WooCommerce stores via the WooCommerce REST API, supporting operations like listing products, orders, and customers.
      176 npm
      MIT

    • PrestaShop MCP (Legacy

      Breczek
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and manage PrestaShop catalogs via the legacy WebService API, covering products, categories, stock, and more across PrestaShop 1.6-9. Provides 45 tools for CRUD operations and read-only generic access.
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different BigCommerce resources: customers, orders, and products. There is no overlap in functionality, and the descriptions specify unique filtering capabilities where applicable, making tool selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get_all_' prefix followed by the resource name (customers, orders, products). This predictable naming scheme enhances readability and usability across the tool set.

    Tool Count2/5

    With only 3 tools, this server feels under-scoped for a BigCommerce API integration. A typical e-commerce platform requires more operations like creating, updating, or deleting resources, making this set too limited for comprehensive agent workflows.

    Completeness2/5

    The tool set is severely incomplete, covering only read operations (get_all) for three core resources. There are significant gaps in CRUD coverage—no create, update, or delete tools—which will likely cause agent failures when attempting full e-commerce management tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources