Dicker Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | env (default, reads the vars above) or gateway (credentials arrive per-request via headers). | env |
| LOG_LEVEL | No | debug | info (default) | warn | error. | info |
| MCP_TRANSPORT | No | stdio (default) or http. | stdio |
| CONDUIT_S2S_SECRET | No | When set, the HTTP transport requires a valid X-Gateway-S2S header on every /mcp request. | |
| DICKERDATA_ACCESS_TOKEN | Yes | Long-lived access token issued by Dicker Data. | |
| DICKERDATA_ACCOUNT_CODE | Yes | Long-lived account code issued by Dicker Data. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| dickerdata_create_orderB | Place a new purchase order with Dicker Data for one or more products. |
| dickerdata_get_order_detailsB | Get details for a single Dicker Data order by order number, account code, or your PO reference. |
| dickerdata_list_ordersC | List Dicker Data orders matching an account code, order number, backorder number, or customer PO number. |
| dickerdata_get_order_serialsB | Get the shipped serial numbers for a Dicker Data order. |
| dickerdata_get_consignment_statusB | Get shipping/tracking status for a Dicker Data consignment number. |
| dickerdata_list_invoicesB | List Dicker Data account invoices within a date range. |
| dickerdata_get_invoice_detailsC | Get line-item detail for a Dicker Data sales order / invoice. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.