explain_drift — marketbasketanalysis mcp MCP Tool
explain_drift
(explain drift) is one of 19 tools on the
marketbasketanalysis mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call explain_drift from your client
- Claude Code marketbasketanalysis mcp explain_drift run in your project directory
- Claude Desktop marketbasketanalysis mcp explain_drift ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor marketbasketanalysis mcp explain_drift ~/.cursor/mcp.json
- VS Code marketbasketanalysis mcp explain_drift .vscode/mcp.json
- Zed marketbasketanalysis mcp explain_drift ~/.config/zed/settings.json
- Windsurf marketbasketanalysis mcp explain_drift ~/.codeium/windsurf/mcp_config.json
- Cline marketbasketanalysis mcp explain_drift ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI marketbasketanalysis mcp explain_drift ~/.gemini/settings.json
- Grok marketbasketanalysis mcp explain_drift .mcp.json (in your project root)
- ChatGPT marketbasketanalysis mcp explain_drift Settings → Connectors → Advanced → Developer mode
- Claude.ai marketbasketanalysis mcp explain_drift Settings → Connectors → Add custom connector
- LangChain marketbasketanalysis mcp explain_drift pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http marketbasketanalysis-mcp https://mcp.marketbasketanalysis.com/mcp
Other tools on this server
- get_recommendations
- find_substitutes
- get_rationale
- get_bundle_for_cart
- propose_subscription_bundle
- score_cross_sell
- score_return_risk
- analyze_basket
- predict_reorder
- forecast_bundle
- get_weekly_plan
- execute_weekly_plan_action
- get_opportunities
- explain_opportunity
- triage_opportunity
- get_drift_alerts
- get_forecast_alerts
- mine_hui_itemsets
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.