Connect SuperPharmacyPlus enriched product knowledge and native BigCommerce storefront shopping as two separate MCP servers.
https://ai.superpharmacyplus.com.au/mcphttps://store-js3ghti4c3-1.mybigcommerce.com/api/mcp (BigCommerce beta; tool list last checked 2026-10-01)Connecting to one endpoint does not connect to the other. Pharmalama does not proxy BigCommerce shopping operations.
ask — structured NLWeb questions and product discovery.search_products — enriched semantic search with pharmacy and catalogue context.get_product — enriched product details by product ID or SKU.find_alternatives — curated alternatives, accessories and compatibility suggestions.get_category — category authority narratives and FAQs.get_brand — brand authority pages and product listings.compare_products — enriched, safety-aware comparisons.These seven Pharmalama tools provide enriched product knowledge and are read-only.
Observed on 2026-10-01: search_products, get_product_details, add_item_to_cart, update_cart_item, remove_item_from_cart, create_checkout_url.
The observed native get_product_details input is productIds: [bigcommerce_product_id], not the id parameter in the generic guide. Refresh the live tools/list because this beta interface can change. This store endpoint did not advertise related_products.
Connect both MCP servers explicitly; discovery links do not install the second connection.
Use superpharmacyplus-knowledge for enriched semantic discovery, FAQs, specifications, comparisons, alternatives and brand/category guides.
Use superpharmacyplus-shopping for live storefront commerce data, product variants/options, shopper carts and checkout handoff. Qualify search_products by server: knowledge takes query; shopping takes term.
Knowledge results expose bigcommerce_product_id, the BigCommerce product entity ID, not a SKU, feed offer ID or variant ID. Re-resolve the chosen item on the shopping server before purchase; the verified native get_product_details input is productIds: [bigcommerce_product_id].
Discover current native tools/list schemas at connection time and after tool changes; fail explicitly on incompatible schemas rather than guessing. The audited tool snapshot is not a current health check.
Ask the shopper to select required variants/options and confirm cart changes. Do not guess a colour, dose or size. inStock alone does not establish purchasability; never promise stock quantities or final freight from the knowledge snapshot.
Keep one isolated native session per shopper. Do not reuse session IDs across customers. Stencil chat widgets require browser-generated session sync and reverse cart sync; re-initialize after login/logout.
Pharmalama public-content compliance filtering does not automatically apply to native BigCommerce tools. Do not make clinical recommendations or advertise restricted medicines merely because native search returns them.
If native shopping is unavailable, keep knowledge access working and link to product_url for website purchase; do not claim a cart was updated. Oscar remains the sole BigCommerce product-metadata writer.
Use the explicit bigcommerce_product_id. The existing numeric id has the same value because the importer preserves the BigCommerce product entity ID. Never substitute a SKU, feed offer ID or variant ID. Resolve live variants/options and confirm the chosen item, quantity and required options before cart changes; do not choose for the shopper.
inStock alone does not establish purchaseability; relay native cart errors accurately. Pharmalama compliance filtering does not automatically apply to native BigCommerce tools or other clients. A future Stencil widget must use per-shopper session sync; never share MCP sessions or tokens between shoppers. Oscar remains the sole product-metadata writer.
A future Stencil widget must obtain generateSessionSyncToken from the shopper's browser (server-to-server generation is blocked) and send it as X-Bc-Storefront-Sync-Token on MCP initialize. This token is one-use and expires after 60 seconds: never cache it. Reverse sync uses X-Bc-Mcp-Stencil-Sync-Code, also one-use with a 60-second TTL; forward it to the browser to apply cart/cookie changes. Re-initialize with a fresh browser token after login or logout. Guest desktop connections do not automatically share the shopper's browser cart or login. Neither public setup requires merchant/admin API keys.
Requires Node.js 18 or later for mcp-remote. BigCommerce MCP is beta. This documented client pattern is not a claim of support for all MCP clients or authenticated shopper sessions.
{
"mcpServers": {
"superpharmacyplus-knowledge": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://ai.superpharmacyplus.com.au/mcp"
]
},
"superpharmacyplus-shopping": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://store-js3ghti4c3-1.mybigcommerce.com/api/mcp"
]
}
}
}Merge these entries under mcpServers in Claude Desktop's claude_desktop_config.json, preserving existing entries, then restart. macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json.
This configuration follows BigCommerce's documented pattern. Direct guest initialize/list/search/details checks passed; no desktop GUI testing is claimed. Other clients must support both connections and independent sessions; no ChatGPT or Gemini setup UI is assumed.
The knowledge manifest and server card contain only knowledge tools. The companion connection record describes both endpoints; it is not an auto-install mechanism or directory-registration guarantee.
pnpm --filter @workspace/api-server check:native-mcp
pnpm --filter @workspace/api-server check:native-mcp -- --list-onlyThe isolated guest probe initializes, checks tools and live schemas, and reads search/details only. It never changes a cart or creates a checkout URL. Failure is reported without disabling knowledge access.
For interactive inspection, run npx @modelcontextprotocol/inspector and connect each endpoint independently using Streamable HTTP. Avoid cart/checkout calls without explicit shopper confirmation.
Inspect tools under each server name. Both servers expose a tool named search_products; distinguish them by server.
Installation guide · Machine-readable connections · Knowledge server manifest · MCP launch announcement · API and MCP docs · llms.txt