A
licenseA
qualityD
maintenanceProvides AI assistants with comprehensive, precise BigCommerce developer documentation via 12 MCP tools, including REST endpoints, GraphQL operations, webhooks, OAuth scopes, and code examples.
12
4 npm
3
MIT
BigCommerce API MCP Server
by isaacgounton
Related Servers
Alternatives to BigCommerce API MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with WooCommerce stores through the WordPress REST API. It provides tools for managing products, orders, customers, shipping, taxes, coupons, reports, and store settings.MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.9 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with commercetools APIs to manage products, categories, orders, carts, and customer data. It provides a comprehensive set of tools for both read-only and full-access operations through secure authentication methods.4MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with WooCommerce stores via the WooCommerce REST API, supporting operations like listing products, orders, and customers.193 npmMIT
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
ActivitySlowing
ResponsivenessLimited data