@marketbasketanalysis/mcp
An MCP server that exposes 19 tools giving AI agents real co-purchase intelligence, basket analysis, forecasting, and merchant-ops tooling from an ecommerce store's order history, supporting Shopify, BigCommerce, WooCommerce, Magento, and OroCommerce.
Discovery: recommend complementary products, find substitutes, and explain why two products are recommended together.
Bundles & insights: complete multi-item carts, propose subscription bundles, score cross-sell strength, return risk, and basket cohesion.
Replenishment & forecasting: predict B2B reorder dates per customer/SKU and forecast weekly bundle demand with buy-quantity recommendations.
Merchant ops: get a ranked weekly plan, execute plan actions, list/explain/triage opportunities, and monitor drift and forecast alerts.
Advanced mining: mine high-utility itemsets from order payloads to find profit-driving product combinations.
Platform flexibility: re-point all tools to a store's backend with one MBA_API_BASE switch, with per-platform coverage and clear not-available errors where routes are unsupported.
Provides AI access to co-purchase intelligence and merchant operations from BigCommerce order history, including product recommendations, bundle building, cross-sell scoring, return-risk analysis, replenishment forecasting, and merchant opportunity management.
Provides AI access to co-purchase intelligence and merchant operations from Shopify order history, including product recommendations, substitutes, bundle proposals, cross-sell and return-risk scoring, reorder prediction, and merchant opportunities.
Provides AI access to co-purchase intelligence from WooCommerce order history, including recommendations, substitutes, rationale, bundle and basket scoring, subscription bundle proposals, reorder prediction, and bundle forecasting.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@marketbasketanalysis/mcp what products are commonly bought together with the yoga mat?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@marketbasketanalysis/mcp
An MCP server that gives any AI agent access to real co-purchase intelligence and merchant ops tooling from an ecommerce merchant's order history. 19 tools across discovery, bundle, insight, replenishment, merchant ops, and advanced mining. Works with Claude Desktop, Claude Code, Cursor, Windsurf, Cline, the OpenAI Agent SDK, and any other host that speaks the MCP stdio protocol. Works for merchants on Shopify, BigCommerce, WooCommerce, Magento, and OroCommerce. See "Platform coverage" below for which tools reach the self-hosted backends.
One npm package serves every marketplace. The server is platform
agnostic, it is an HTTP client that calls a store's MBA backend over
the public REST API. You re-point the whole server at any store with a
single switch (MBA_API_BASE, see below). Most tools work on all five
platforms; a handful depend on a backend route that not every platform
ships yet. Per-tool marketplace coverage is the
Tool catalog "Marketplace" column.
Why this exists
When a customer asks an AI shopping agent "what goes with the gym backpack?" the agent should give a real answer based on the merchant's actual order data, not a generic "you might also like" guess. When a merchant asks Claude "what should I work on this week?" the agent should pull from a ranked weekly plan, not invent tasks. This server makes both of those flows available to any MCP host in one line of config.
Related MCP server: dentro MCP
5-line install (Claude Desktop)
{
"mcpServers": {
"marketbasketanalysis": {
"command": "npx",
"args": ["-y", "@marketbasketanalysis/mcp"],
"env": { "MBA_API_KEY": "mba_live_YOUR_KEY_HERE" }
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS), restart Claude Desktop, the marketbasketanalysis server
appears in the tools list with all 19 tools.
Zero-install: the hosted endpoint
The same server runs hosted at
https://mcp.marketbasketanalysis.com/mcp (MCP streamable HTTP).
Nothing to install; send your key as a bearer header instead of an
env var:
claude mcp add --transport http marketbasketanalysis \
https://mcp.marketbasketanalysis.com/mcp \
--header "Authorization: Bearer mba_live_YOUR_KEY_HERE"Works with any remote-capable MCP client (Claude Code, Cursor,
Smithery, custom agents). Optional headers: X-MBA-Base re-points at
another MBA-operated plane (for example
https://bigcommerce.marketbasketanalysis.com); X-MBA-Platform
mirrors the MBA_PLATFORM env var. Self-hosted WooCommerce and Magento
stores are not reachable from the hosted endpoint by design, use the
npx install above with MBA_API_BASE pointed at your own site.
Point the server at your store (MBA_API_BASE)
The base URL is per-store configuration. By default the server talks
to the shared hosted backend at https://app.marketbasketanalysis.com.
If your data lives anywhere else, a BigCommerce store, a self-hosted
backend, or a staging instance, set MBA_API_BASE so every tool
reaches your own data plane:
{
"mcpServers": {
"marketbasketanalysis": {
"command": "npx",
"args": ["-y", "@marketbasketanalysis/mcp"],
"env": {
"MBA_API_KEY": "mba_live_YOUR_KEY_HERE",
"MBA_API_BASE": "https://your-store-backend.example.com"
}
}
}
}MBA_API_BASE is the single switch that re-points the whole server;
all 19 tools route through it. The value must be an https:// URL for
non-local hosts (loopback, private, link-local, and metadata-service
hosts are refused). For local development against a backend on
localhost, set ALLOW_LOCAL_API_BASE=1 to allow an http://localhost
base. Env-var changes take effect at server startup, so restart your
MCP host after editing the value.
MBA_API_BASE per platform
The base URL is per-store configuration. Shopify, BigCommerce, and OroCommerce stores are served by the shared hosted backend, so they use the default. WooCommerce and Magento run the backend locally inside the store install, so point the server at the store's own domain:
Platform |
|
Shopify | unset (hosted default |
BigCommerce | unset (hosted default) |
OroCommerce | unset (thin hosted client, same hosted backend) |
WooCommerce |
|
Magento |
|
Platform coverage
The server writes canonical /api/v1/... paths and rewrites them per
platform, because WooCommerce and Magento run the backend inside the
store on their own REST conventions (marketbasketanalysis/v1 and
V1/marketbasketanalysis respectively).
10 of the 19 tools reach WooCommerce and Magento: the six that derive
from /recommendations (get_recommendations, get_bundle_for_cart,
score_cross_sell, analyze_basket, propose_subscription_bundle,
score_return_risk), plus find_substitutes, get_rationale,
forecast_bundle, and predict_reorder.
The other 9 are the merchant-ops surface: get_opportunities,
triage_opportunity, get_weekly_plan, execute_weekly_plan_action,
get_drift_alerts, get_forecast_alerts, explain_opportunity,
explain_drift, and mine_hui_itemsets. Those endpoints do not exist on
the self-hosted backends. Calling one there returns a clear "not
available on this platform" error naming the endpoint, with no network
round trip, rather than an opaque 404.
For step-by-step install (config file location per OS, where to mint an API key, troubleshooting):
Claude Desktop: dist/mcp/claude-desktop-setup.md
Cursor: dist/mcp/cursor-setup.md
Windsurf: dist/mcp/windsurf-setup.md
Authentication
The server reads MBA_API_KEY from the environment your MCP host
passes in and sends it as a Bearer token on every request. To get a
key:
Open the MarketBasketAnalysis admin (Shopify app drawer, or BigCommerce / WooCommerce / Magento / OroCommerce admin).
Click "API keys" in the left nav.
Click "Create key", name it, and copy the
mba_live_value (it is shown once).
Keys are per-shop, revocable, and rotated from the same screen. Only the SHA-256 hash is stored, so re-mint if a key leaks.
Auth model differs per marketplace, the MCP server abstracts it, but worth knowing:
Shopify, BigCommerce:
Bearer mba_live_...straight through. This is the common path.WooCommerce:
Beareragainst a Woo-minted key, which must carry thecustomer_datascope forpredict_reorder.Magento: tools reach the store over the Magento REST surface (
/V1/marketbasketanalysis/*and/V1/mba/*); some routes are admin-token / ACL scoped on the store side.OroCommerce: the store sits behind the platform OAuth2 firewall for
/api/routes; the hosted backend the thin client proxies to is what the MCP server actually calls, so themba_live_key still applies.
Tool catalog
19 tools, organized into the four Basket AI agent roles plus two operational groups. The Marketplace column states which backends ship the route the tool calls, which is not the same as which backends this server can currently REACH: see "Platform coverage" above. "All five" means Shopify, BigCommerce, WooCommerce, Magento, OroCommerce.
Discovery
Tool | Description | Required params | Marketplace |
| Complementary products for a single product. |
| All five |
| Replacement options when a product is unavailable. |
| All five |
| One-sentence "why" for a recommendation pair. |
| All five |
Bundle
These derive everything from /recommendations (the server composes
the bundle/scoring logic client-side), so they need no extra backend
route and work everywhere.
Tool | Description | Required params | Marketplace |
| Missing kit components for a multi-item cart. |
| All five |
| Recurring subscription kit proposal. |
| All five |
Insight
Also /recommendations-derived, so universal.
Tool | Description | Required params | Marketplace |
| Strength verdict for a (a, b) pair. |
| All five |
| Bundle return-risk score. |
| All five |
| Cohesion score for a proposed bundle. |
| All five |
Replenishment + forecasting
Tool | Description | Required params | Marketplace |
| B2B reorder cadence per customer / SKU. |
| Shopify, BigCommerce, WooCommerce, Magento. Hidden when |
| Weekly Holt-Winters forecast + buy quantity. |
| Shopify, BigCommerce, Magento ( |
Merchant ops
These call Bearer /api/v1 routes that ship on BigCommerce today.
Shopify serves opportunities, drift, and the weekly plan through its
embedded admin views rather than an /api/v1 route, so these tools
resolve against a BigCommerce backend. The one exception is
/explain-opportunity, which now ships on BigCommerce and Shopify;
/explain-drift remains BigCommerce only. The tools surface a clean
upstream 404 on platforms that lack the route.
Tool | Description | Required params | Marketplace |
| Ranked weekly action list. | (none) | BigCommerce |
| Dispatch a specific action (confirm-gated). |
| BigCommerce |
| Mined opportunities, ranked. | (none) | BigCommerce |
| Stats (support / confidence / lift / sample count) plus a templated "why this is a good cross-sell" narrative for one opportunity. |
| BigCommerce, Shopify |
| Activate / pause / archive (confirm-gated). |
| BigCommerce ( |
| Rules whose confidence has drifted. | (none) | BigCommerce |
| Stats plus a templated "why this pair drifted" narrative for one drift alert (degrades gracefully for a disappeared pair). |
| BigCommerce |
| Bundles at risk of stockout / demand drop. | (none) | BigCommerce |
Advanced mining
Tool | Description | Required params | Marketplace |
| High-utility itemset mining (Plus / Enterprise). |
| Shopify, BigCommerce, WooCommerce, OroCommerce. Plus / Enterprise tier. |
Example prompts per tool
Paste any of these into a Claude Desktop / Claude Code / Cursor chat after wiring up the server:
get_recommendations: "Use marketbasketanalysis to find what customers also buy with the gym backpack (product 8472918765)."find_substitutes: "The DSLR body is out of stock. What is a good substitute?"get_rationale: "Why is the water bottle recommended with the gym backpack?"get_bundle_for_cart: "I have a camera body, 32GB SD card, and a tripod in my cart. What is likely missing to make this a complete kit?"propose_subscription_bundle: "Build a monthly subscription kit for customer 9876."score_cross_sell: "Is a cleaning kit a good cross-sell for the DSLR camera body?"score_return_risk: *"What is the return risk of the camera + lenstripod + bag bundle?"*
analyze_basket: "I am thinking of bundling camera + lens + SD card + bag. Based on actual customer data, is that a strong bundle?"predict_reorder: "What is Acme Corp (customer 7654321) due to reorder this week?"forecast_bundle: "Forecast bundle b-camera-kit for the next 12 weeks and recommend a buy quantity."get_weekly_plan: "What is on my weekly plan?"execute_weekly_plan_action: "Run action a-42 from my weekly plan, confirmed."get_opportunities: "Show me my top three proposed opportunities."explain_opportunity: "Why is opportunity opp-17 a good cross-sell?"triage_opportunity: "Activate opportunity opp-17, confirmed."get_drift_alerts: "Are any of my rules drifting?"explain_drift: "Why did the pair in drift alert alert-7 drift?"get_forecast_alerts: "Which bundles are at risk of stockout?"mine_hui_itemsets: "Mine top-20 high-utility itemsets from this 90-day order payload." (Plus / Enterprise tier)
Per-tool narrative docs live in the cookbook.
Env vars
Variable | Required | Default | Notes |
| yes | -- | The |
| no |
| Per-store base URL. Set this for BigCommerce, self-hosted, or staging backends so the server points at your data plane. Must be |
| no |
| Set to |
| no | -- | Opt-in error telemetry (merchant-controlled) |
| no | -- | Set to |
| no | -- | Set to |
Development
git clone https://github.com/48x-ai/marketbasketanalysis
cd marketbasketanalysis
pnpm install
pnpm --filter ./packages/mcp typecheck
pnpm --filter ./packages/mcp test
pnpm --filter ./packages/mcp dev # tsx-based local run
pnpm --filter ./packages/mcp build # emit ./distAdding a new tool
Each tool is a self-contained module under src/tools/. To add one:
Create
src/tools/myNewTool.tsexportingdefinitionandhandler. Mirror the structure ofsrc/tools/getRecommendations.tsfor a simple GET, orsrc/tools/triageOpportunity.tsfor a POST with a confirm gate.Register it in
src/tools/index.tsby importing and adding the module to theallModulesarray.Add tests in
src/tools/myNewTool.test.ts, covering: missing-key reply, happy path, and at least one upstream-error path. Mirrorsrc/tools/findSubstitutes.test.ts.Document it in the table above and in
dist/mcp/smithery.yaml.
Distribution artifacts
The dist/mcp/ directory at the monorepo root holds the install
samples (Claude Desktop, Cursor, Windsurf), the Smithery YAML, and
the Anthropic marketplace submission content. See
dist/mcp/README.md for the full layout.
Publishing
Tag-based publish via the monorepo-root
.github/workflows/publish-mcp.yml workflow. Bump the version in
packages/mcp/package.json (keep server.json and src/index.ts in
sync), merge to main, then tag mcp-v$VERSION and push the tag. The
workflow runs typecheck, test, build, a tag/version match check, then
npm publish --access public --provenance using the NPM_TOKEN repo
secret. A workflow_dispatch manual trigger is available for rescue
runs.
The full operator checklist, including the one-time NPM_TOKEN setup
and a no-CI manual publish fallback, lives in
docs/RELEASE.md.
Troubleshooting
Symptom | Cause / fix |
Server does not appear in tool drawer | JSON typo or |
"Error: MBA_API_KEY environment variable not set" |
|
"MBA API 401" | Key revoked or wrong; mint a fresh one. |
"MBA API unreachable" | Network reach failed; check |
Tool times out on first call | First |
"MBA API returned malformed response" | Upstream backend drift; set |
| The tool is platform-gated: it registers when |
For deeper diagnostics see each per-IDE setup doc under
dist/mcp/.
License
UNLICENSED, proprietary.
Available Tools
19 toolsanalyze_basketAInspect
Run market-basket analysis on a proposed basket / bundle to score its cohesion. Given 2+ products, returns a cohesion score 0..1 representing how strongly they bind together (their affinity) in the merchant's order data. Use this to vet a proposed bundle BEFORE recommending it, so agents can avoid suggesting bundles that look plausible but have no statistical signal. Also useful for 'is this a good bundle?', 'analyze this basket', or 'do these products go together?' questions.
Inputs: product_ids (required).
execute_weekly_plan_actionAInspect
Execute a specific action from the merchant's weekly plan (publish bundle, run mining job, archive rule, etc.). Idempotent by action_id, safe to retry. Use this AFTER the merchant has confirmed which action from get_weekly_plan they want to run; do not call preemptively. Merchant-ops surface: BigCommerce today; on other platforms merchants manage this from the admin, and the tool returns a clear not-available message.
Inputs: confirm (required), action_id (required).
explain_driftAInspect
Explain ONE drift alert: return its prior and current confidence (plus support, lift, and order sample count when the rule is still live) and a short plain-language narrative of how the pair moved versus the prior mining run. Use this when a merchant asks 'why did this pair drift?', 'explain this alert', or 'what changed for these two products?' after seeing it in get_drift_alerts. Different from get_drift_alerts: that lists the feed, this drills into a single alert_id with the change spelled out in a sentence. Handles a disappeared pair gracefully (only the prior confidence is available). BigCommerce only today.
Inputs: alert_id (required).
explain_opportunityAInspect
Explain ONE mined opportunity: return its support, confidence, lift, and order sample count plus a short plain-language narrative of why the pair is a good cross-sell. Use this when a merchant asks 'why is this a good cross-sell?', 'explain this opportunity', or 'why should I bundle these?' after seeing it in get_opportunities. Different from get_opportunities: that lists the ranked set, this drills into a single opportunity_id with the stats spelled out in a sentence. Different from get_rationale: rationale is a generic pair 'why', this is the specific mined opportunity's own numbers. BigCommerce only today.
Inputs: opportunity_id (required).
find_substitutesAInspect
For a given product, recommend the top substitute items that could REPLACE it (not complement it). Substitutes are the inverse of cross-sell: this answers 'what to buy instead', not 'what to buy with'. Use this when the user asks 'what's a substitute for X?', 'X is out of stock, what's a good alternative?', 'recommend a replacement for Y', 'find an equivalent product', or when a procurement agent needs to swap an unavailable SKU. Returns a ranked list with a similarity score and a reason (context_similar / category_match / vendor_match). Works for all five platforms: Shopify, BigCommerce, WooCommerce, Magento, and OroCommerce.
Inputs: product_id (required), limit.
forecast_bundleAInspect
For an inventory, purchasing, or merchant-ops agent: forecast weekly sales and recommend a buy quantity for a specific bundle over a configurable horizon. Uses additive Holt-Winters on the bundle's stored historical sales (demand forecasting). Use this when the agent asks 'how many of bundle X should I order?', 'what should I stock for the next N weeks?', 'what's the demand outlook for bundle Y?', or 'forecast the next 8 weeks for the camera bundle'.
Inputs: bundle_id (required), horizon_weeks.
get_bundle_for_cartAInspect
Given a list of products already in the cart, recommend products that frequently bundle with the cart to complete a high-confidence bundle. This is multi-item basket analysis for cart completion. Use when the user describes a multi-item cart and asks 'what else do I need?', 'what completes this set?', 'what's missing from this bundle?', 'recommend add-ons for this cart', or similar. Different from get_recommendations: this takes MULTIPLE products and returns items that pair with the cart as a whole, not single-item pairings.
Inputs: product_ids (required), limit.
get_drift_alertsAInspect
For a merchant-ops or analytics agent: list active drift alerts, the recommendation rules whose confidence has materially changed (weakened, strengthened, disappeared, emerged) versus the prior mining job. Use this when a merchant asks 'what's changed?', 'is my model still accurate?', 'are any rules drifting?', or wants to investigate a SKU swap / seasonal shift. Merchant-ops surface: BigCommerce today; on other platforms merchants manage this from the admin, and the tool returns a clear not-available message.
Inputs: limit, severity.
get_forecast_alertsAInspect
For an inventory or merchant-ops agent: list forecast-based alerts, the bundles with stockout risk, demand drop, demand spike, or an unreliable forecast curve. Use this when a merchant asks 'what's at risk of stockout?', 'which bundles are losing demand?', 'do I need to reorder anything?', or 'what should I restock?'. Pair with forecast_bundle to drill into a specific bundle. Merchant-ops surface: BigCommerce today; on other platforms merchants manage this from the admin, and the tool returns a clear not-available message.
Inputs: kind, limit, severity.
get_opportunitiesAInspect
List the merchant's ranked bundle / cross-sell opportunities mined from order history, with support / confidence / lift / revenue-weighted score. Use this when a merchant asks 'what are my top opportunities?', 'show me the best bundles I haven't published yet', or 'what should I prioritize?'. Pair with triage_opportunity to act on a specific one. Merchant-ops surface: BigCommerce today; on other platforms merchants manage this from the admin, and the tool returns a clear not-available message.
Inputs: limit, status.
get_rationaleAInspect
Fetch the one-sentence rationale for why product B is recommended alongside product A. Returns a short merchandiser-grade explanation ('these are commonly bought together by customers buying X') suitable for surfacing in a recommendation tile or chat reply. Use this after get_recommendations / get_bundle_for_cart when the agent or user asks 'why are these recommended together?' or 'explain this pairing'.
Inputs: product_id (required), related_product_id (required).
get_recommendationsAInspect
For a given product, recommend the top complementary, frequently-bought-together products customers also bought, based on mined order-history association rules. This is the single-product cross-sell tool. Use this when the user asks 'what goes with X?', 'what should I bundle with X?', 'what do customers also buy with X?', 'recommend products to cross-sell with X', or similar single-product co-purchase questions. Works for all five platforms: Shopify, BigCommerce, WooCommerce, Magento, and OroCommerce.
Inputs: product_id (required), limit.
get_weekly_planAInspect
Fetch the current weekly action plan for the merchant: a ranked list of typed actions (publish opportunity, retire stale bundle, reorder inventory, investigate drift, etc.) the merchant should take this week. Use this when a merchant asks 'what should I work on this week?', 'what's on my plate?', 'show me my weekly plan', or wants a summary of pending tasks before opening the admin. Merchant-ops surface: BigCommerce today; on other platforms merchants manage this from the admin, and the tool returns a clear not-available message.
Inputs: no named parameters.
mine_hui_itemsetsAInspect
Run high-utility itemset (HUI) mining on a caller-supplied payload of orders + per-line unit_profit. Returns top-K itemsets ranked by aggregate utility (sum of profit across all occurrences). Use this when an agent needs to evaluate which item combinations drive the most profit (not just frequency) for a specific time window or product subset. Plus or Enterprise tier required on the merchant account.
Inputs: orders (required), top_k, min_utility.
predict_reorderAInspect
For a sales-rep or inventory / account-management agent: predict when a B2B customer / account is due to reorder. Returns predicted next-order dates for every SKU the customer has ordered >=2 times, with confidence based on the regularity of their cadence (reorder prediction / replenishment forecasting). Bucketed into 'overdue' / 'due_soon' / 'on_track' / 'not_predictable'. Use this when the agent asks 'what's Acme Corp due to reorder?', 'when will customer X need more of Y?', 'show me stockout risks for my B2B accounts', or for proactive replenishment workflows. Works on the Shopify, BigCommerce, WooCommerce, and Magento backends. Not available on OroCommerce.
Inputs: customer_id (required), product_id.
propose_subscription_bundleAInspect
Propose a recurring subscription bundle for a customer based on their first-order items. Given 1-5 seed products the customer has bought, returns a recurring subscription bundle (3-6 items) of the seeds plus complementary products, with a predicted cadence (median days between reorders), a 0..1 confidence score, and a rough monthly_value when prices are known. Use this when a merchant agent asks 'what should they subscribe to?', 'build a monthly subscription bundle from this order', 'propose a subscription bundle', 'recommend a recurring replenishment bundle', or 'what's the right subscription frequency for this customer?'. If a customer_id is supplied the tool blends in the customer's per-SKU reorder cadence; without one it falls back to the seed catalog cohesion alone. Works for all five platforms: Shopify, BigCommerce, WooCommerce, Magento, and OroCommerce (the optional reorder-cadence blend needs a customer_id and is not available on OroCommerce).
Inputs: seed_product_ids (required), kit_size, customer_id, cadence_days.
score_cross_sellAInspect
Score the cross-sell strength (product affinity) between two specific products. Returns the confidence the merchant's real co-purchase data supports for the pair, or a clear 'no signal' result when there's no qualifying rule. Use this to validate a proposed pair before recommending it, or to answer 'is X a good cross-sell for Y?', 'how strong is the affinity between X and Y?', or 'how often are X and Y bought together?'.
Inputs: product_a (required), product_b (required).
score_return_riskAInspect
Predict return risk for a candidate bundle of 2-6 products. Returns the composite bundle return rate (max of items, since one returned item typically returns the whole bundle), each item's historical return rate, and a low/medium/high risk recommendation. Use this when the user asks 'will this bundle get returned?', 'predict return risk for these items', 'fashion bundle risk', 'is this set risky to ship together?', or when an agent is composing a bundle and wants to verify it won't tank the merchant's return KPIs. Backed by return-aware mining over the merchant's real order + refund history.
Inputs: product_ids (required), threshold.
triage_opportunityAInspect
Pause, activate, or archive a specific opportunity from get_opportunities. State-mutating; guarded by confirm=true. Use this after the merchant has explicitly picked an opportunity to act on. Pass action='activate' to publish a proposed rule, 'pause' to temporarily hide an active one, 'archive' to permanently retire it. Merchant-ops surface: BigCommerce today; on other platforms merchants manage this from the admin, and the tool returns a clear not-available message.
Inputs: action (required), confirm (required), opportunity_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Most tools are clearly differentiated by resource and action (single-product vs cart vs subscription, list vs explain vs act), and several descriptions explicitly call out differences from related tools. However, the cluster of explanation tools (get_rationale, explain_opportunity, explain_drift) and the several scoring/analysis tools (score_cross_sell, analyze_basket, score_return_risk) could still cause minor selection confusion from names alone.
All tool names follow snake_case verb_noun conventions and are mostly predictable (get_*, explain_*, score_*). There are minor inconsistencies: related recommendation tools use different verbs (get_recommendations, find_substitutes, propose_subscription_bundle, get_bundle_for_cart), and predict_reorder vs forecast_bundle split an otherwise uniform forecasting concept.
With 19 tools, the server sits in the 16-25 range, which feels heavy and exceeds the ideal well-scoped 3-15 band. The count is defensible given the broad domain coverage, but agents will need to navigate a large surface to find the right tool.
The tool surface covers a comprehensive market-basket workflow: recommending, substituting, scoring, explaining, mining, alerting, forecasting, and acting on opportunities. Minor gaps exist—such as no direct tool for managing custom rules beyond triage and no bulk scoring—but the core domain is well covered with no critical dead ends.
Maintenance
Related MCP Connectors
Connect AI to store orders, products and inventory with scoped access and human approvals.
The E-commerce Marketplace For Every AI Agent. A Governed Catalog Of 600M+ US Products.
The E-commerce Marketplace For Every AI Agent. A Governed Catalog Of 600M+ US Products, Plus Four Agent Ready Capabilities Search, Price Comparison, Product-Vs-Product, And Detailed Q&A.
AI-agent product catalog: search, lookup & purchase routing over verified merchant data.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI agents to manage e-commerce operations across multiple platforms (Shopify, WooCommerce, Stripe, MercadoLibre) through a conversational interface.4112 npmMIT

dentro MCPofficial
AlicenseAqualityDmaintenanceProvides structured commerce data for AI agents, enabling real-time product searches and brand discovery across 22,000+ DTC brands without scraping or hallucination.542 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to browse product catalogs, search products with filters, and initiate checkouts, generating order summaries and checkout URLs.-
- AlicenseNot gradedqualityCmaintenanceEnables AI shopping agents to search products, check stock, apply promotions, manage cart sessions, and create cryptographically signed checkout sessions on e-commerce storefronts, while giving merchants analytics into agent intent and catalog demand gaps.MIT