Back to Browse

Dicker Data MCP Server

Developer ToolsUse Caution4.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for Dicker Data's B2B partner/reseller REST API — pricing, orders, and invoices.

About

MCP server for Dicker Data's B2B partner/reseller REST API — pricing, orders, and invoices.

Security Report

4.8
Use Caution4.8High Risk

A well-architected MCP server for Dicker Data's B2B API with strong authentication and credential handling. The codebase demonstrates good security practices including proper AsyncLocalStorage-based credential isolation for multi-tenant scenarios, careful AccessKey refresh logic, and appropriate input validation. Minor code quality issues and one informational finding do not materially impact security. Supply chain analysis found 4 known vulnerabilities in dependencies (2 critical, 0 high severity).

7 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Dicker Data partner account codeOptional

Environment variable: DICKERDATA_ACCOUNT_CODE

Dicker Data long-lived API access token (obtained from Dicker Data integration support)Required

Environment variable: DICKERDATA_ACCESS_TOKEN

Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.Optional

Environment variable: MCP_TRANSPORT

Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.Optional

Environment variable: AUTH_MODE

Log verbosity: debug, info, warn, errorOptional

Environment variable: LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-wyre-ai-dicker-data-mcp": {
      "env": {
        "AUTH_MODE": "your-auth-mode-here",
        "LOG_LEVEL": "your-log-level-here",
        "MCP_TRANSPORT": "your-mcp-transport-here",
        "DICKERDATA_ACCESS_TOKEN": "your-dickerdata-access-token-here",
        "DICKERDATA_ACCOUNT_CODE": "your-dickerdata-account-code-here"
      },
      "args": [
        "-y",
        "@wyre-ai/dicker-data-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

Configuration

Env varDescription
DICKERDATA_ACCOUNT_CODELong-lived account code issued by Dicker Data.
DICKERDATA_ACCESS_TOKENLong-lived access token issued by Dicker Data.
MCP_TRANSPORTstdio (default) or http.
AUTH_MODEenv (default, reads the vars above) or gateway (credentials arrive per-request via X-DickerData-Account-Code / X-DickerData-Access-Token headers, injected by the Conduit gateway).
CONDUIT_S2S_SECRETWhen set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request.
LOG_LEVELdebug | info (default) | warn | error.

Tools

Pricing

  • dickerdata_get_pricing - live pricing + stock-on-hand for one or more product codes.
  • dickerdata_get_price - detailed pricing for a single product code at a given quantity.

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.

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 --noEmit

Docker

docker build -t dicker-data-mcp .
docker run -p 8080:8080 -e DICKERDATA_ACCOUNT_CODE=... -e DICKERDATA_ACCESS_TOKEN=... dicker-data-mcp

Reviews

No reviews yet

Be the first to review this server!