Dicker Data MCP Server
An MCP server for Dicker Data's B2B distributor API, letting AI assistants look up pricing/stock, place and track orders, and retrieve invoices on behalf of a reseller account.
Price & stock lookup —
dickerdata_get_pricingfor one or more product codes, ordickerdata_get_pricefor a single code (both use the PricingRequest datafeed, which may lag live account pricing and has no quantity-based pricing).Place orders —
dickerdata_create_orderwith line items (part number, quantity, optional unit price), PO reference, notes, and optional delivery address/attention.Review orders —
dickerdata_get_order_detailsfor a single order anddickerdata_list_ordersfiltered by account, order, backorder, or customer PO number.Track shipments —
dickerdata_get_order_serialsfor shipped serial numbers anddickerdata_get_consignment_statusfor consignment tracking status.Invoicing —
dickerdata_list_invoicesfor a date range anddickerdata_get_invoice_detailsfor line-item detail of a sales order/invoice.
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., "@Dicker Data MCP Server What's the live price and stock for product code AP-1234?"
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.
Dicker Data MCP Server
MCP server for Dicker Data's B2B partner/reseller REST API - pricing and stock lookup, order placement and tracking, and invoices, for AI assistants and the WYRE Conduit gateway.
Authentication
Dicker Data does not offer self-serve API signup. Request access from integration.support@dickerdata.com.au or services.sales@dickerdata.com.au to receive a long-lived AccountCode + AccessToken pair.
Every real API call additionally requires a short-lived AccessKey, obtained by exchanging the AccountCode/AccessToken via POST /api/AccessKeyRequest. This server handles that exchange (and its refresh, on expiry) internally - callers only ever need to supply the long-lived credentials.
Related MCP server: ECOUNT MCP Server
Configuration
Copy .env.example and set the variables below.
Variable | Required | Description |
| For stdio and | Long-lived account code issued by Dicker Data. Gateway mode does not read this. |
| For stdio and | Long-lived access token issued by Dicker Data. Gateway mode does not read this. |
| No |
|
| No |
|
| Yes for HTTP | Service-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder. Compose will not start without it. Never commit a real value. |
| No | Set to exactly |
| No | Bind address when a secret is configured. Unset means |
| No | HTTP port. Defaults to |
| No |
|
/health stays unauthenticated, does not require X-Gateway-S2S, and does not read vendor credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
HTTP authentication
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The value is t=<unix seconds>,v1=<hex hmac-sha256>. The hex digest is HMAC-SHA256 over the exact ASCII string t=<unix seconds> (the same prefix that appears in the header), keyed with CONDUIT_S2S_SECRET, encoded as 64 lowercase hex characters. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401. The secret is never written to logs or the response.
X-Gateway-S2S: t=1710000000,v1=<64 lowercase hex chars>Known placeholders are rejected at startup and do not count as a configured secret: changeme, change-me, secret, example, placeholder, replace-me, your-secret, your-s2s-secret, s2s-secret, replace-with-a-real-secret. Generate a value with openssl rand -hex 32.
In AUTH_MODE=gateway, /mcp also requires X-DickerData-Account-Code and X-DickerData-Access-Token. Those headers are the only Dicker Data credentials for that request. A request missing either returns 401 and does not fall back to DICKERDATA_ACCOUNT_CODE / DICKERDATA_ACCESS_TOKEN.
Tools
Pricing
dickerdata_get_pricing- PricingRequest price-list (datafeed) pricing + stock-on-hand for one or more product codes. May lag your live account price and stock; dimensions may be null.dickerdata_get_price- PricingRequest price-list (datafeed) pricing + stock for a single product code. Same feed asdickerdata_get_pricing, may lag your live account price and stock; no quantity-based pricing.
Orders
dickerdata_create_order- place a purchase order.dickerdata_get_order_details- look up a single order.dickerdata_list_orders- list orders matching account code / order / backorder / PO number.dickerdata_get_order_serials- shipped serial numbers for an order.dickerdata_get_consignment_status- shipping/tracking status for a consignment.
Account
dickerdata_list_invoices- invoices within a date range.dickerdata_get_invoice_details- line-item detail for a sales order/invoice.
Known issues
WYREAI-592: Dicker Data's POST /api/DickerData/GetPrice requires an undocumented HTTP Authorization header, so dickerdata_get_price uses GET /api/PricingRequest instead (a price-list feed that may lag the live account price and stock; no quantity-based pricing). The live endpoint is not used until the Authorization scheme is known. dickerdata_create_order may hit the same "Missing Request Header/Authorization" 401 until Dicker confirms the auth scheme.
Scope
This is a v1 / MVP surface covering the core distributor workflow (pricing, ordering, tracking, invoicing). Explicitly out of scope for now: Microsoft CSP/ESD subscription management, Autodesk subscriptions, and annuity-order endpoints - these are much larger, vendor-specific surfaces distinct from core distribution. They can be added as a follow-up if there's demand.
Development
npm install
npm run build
npm test
npm run lint # tsc --noEmitDocker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode the account code and access token arrive on each request as X-DickerData-Account-Code and X-DickerData-Access-Token; they are not read from the environment.
docker build -t dicker-data-mcp .
docker run \
-e CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" \
-p 127.0.0.1:8080:8080 \
dicker-data-mcpDo not pass a known placeholder such as your-s2s-secret or changeme. Startup treats those as unset and exits. Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, does not pass DICKERDATA_ACCOUNT_CODE or DICKERDATA_ACCESS_TOKEN, and publishes 127.0.0.1:8080:8080. A project .env is interpolation only — do not add env_file to the gateway service.
CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" docker compose upSingle-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses DICKERDATA_ACCOUNT_CODE and DICKERDATA_ACCESS_TOKEN:
docker run \
-e CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" \
-e AUTH_MODE=env \
-e DICKERDATA_ACCOUNT_CODE=your-account-code \
-e DICKERDATA_ACCESS_TOKEN=your-access-token \
-e MCP_HTTP_HOST=0.0.0.0 \
-p 127.0.0.1:8080:8080 \
dicker-data-mcpLocal HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) is overridden and that override is logged:
MCP_ALLOW_INSECURE_DEV=1 npm run start:httpA signed gateway request:
curl -sS http://127.0.0.1:8080/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-H "x-gateway-s2s: $X_GATEWAY_S2S" \
-H "x-dickerdata-account-code: $DICKERDATA_ACCOUNT_CODE" \
-H "x-dickerdata-access-token: $DICKERDATA_ACCESS_TOKEN" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Available Tools
9 toolsdickerdata_create_orderB
Place a new purchase order with Dicker Data for one or more products.
Inputs: items (required), notes, customerPORef, deliveryAddress, +1 more.
dickerdata_get_consignment_statusB
Get shipping/tracking status for a Dicker Data consignment number.
Inputs: consignmentNumber (required).
dickerdata_get_invoice_detailsC
Get line-item detail for a Dicker Data sales order / invoice.
Inputs: salesOrderNumber (required), salesOrderNumberSuffix, includeCustomerQualification.
dickerdata_get_order_detailsB
Get details for a single Dicker Data order by order number, account code, or your PO reference.
Inputs: accountCode, orderNumber, customerPORef.
dickerdata_get_order_serialsB
Get the shipped serial numbers for a Dicker Data order.
Inputs: orderNumber (required), orderSuffix.
dickerdata_get_priceA
Look up Dicker Data PricingRequest price-list (datafeed) pricing and stock-on-hand for a single product code. UnitPrice and SOH come from Dicker's PricingRequest feed and may lag your live account price and stock; dimensions may be null. No quantity-based pricing (PricingRequest has no quantity field). Currently uses the same PricingRequest feed as dickerdata_get_pricing, not Dicker's live GetPrice endpoint.
Inputs: productCode (required).
dickerdata_get_pricingA
Look up Dicker Data PricingRequest price-list (datafeed) pricing and stock-on-hand for one or more product codes. UnitPrice and SOH come from Dicker's PricingRequest feed and may lag your live account price and stock; dimensions may be null.
Inputs: productCodes (required).
dickerdata_list_invoicesB
List Dicker Data account invoices within a date range.
Inputs: endDate, startDate.
dickerdata_list_ordersC
List Dicker Data orders matching an account code, order number, backorder number, or customer PO number.
Inputs: accountCode, orderNumber, backorderNumber, customerPONumber.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Most tools target distinct resources/actions, and descriptions clarify the order vs invoice vs serial distinctions. The main weakness is dickerdata_get_pricing vs dickerdata_get_price, which are nearly identical tools differing only by single vs multiple product codes and both use the same PricingRequest feed.
All nine tools use a consistent dickerdata_ prefix followed by a clear snake_case verb_noun pattern such as get_order_details, list_invoices, and create_order. The convention is predictable throughout.
Nine tools is a well-scoped set for a distributor ordering/pricing server, with each tool covering a distinct operational need. The count is neither thin nor bloated.
The surface covers pricing/stock lookup, order creation, order and invoice retrieval, consignment tracking, and serial numbers. Minor gaps exist around product catalog/search and order update/cancel operations, but core account workflows are represented.
Maintenance
Related MCP Connectors
Manage Shipday orders, drivers, driver earnings, reports from your AI assistants.
Live data for AI agents. Search the catalog, read the price, call the tool; keys stay server-side.
Query your books, company data, business health, and ship invoices from your AI assistant.
Enable AI assistants to interact seamlessly with Feeef e-commerce stores, products, and orders usi…
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceProvides AI assistants with access to the SoftwareOne Marketplace API, enabling natural language queries of products, orders, and invoices with full RQL support for filtering and searching across 263 API endpoints.-
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with ECOUNT ERP through natural language, providing tools for products, inventory, sales, purchases, and more.236MIT
- AlicenseAqualityBmaintenanceEnables natural-language interaction with the Yango Tech Retail B2B API to create and track orders, browse product catalogs, and manage prices, discounts, and stock levels across darkstores.1676 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to natively interact with Dolibarr ERP/CRM through its REST API, providing over 30 tools for managing customers, contacts, products, quotes, orders, invoices, stock, projects, contracts, interventions, and PDF generation, while supporting complex workflow orchestration and read-only security modes.MIT