digikey-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIGIKEY_MODE | No | Operational mode: offline (default), sandbox, or production. | offline |
| DIGIKEY_CLIENT_ID | No | Your DigiKey API client ID for sandbox or production mode. | |
| DIGIKEY_ACCOUNT_ID | No | Your DigiKey account ID for sandbox or production mode. | |
| DIGIKEY_CLIENT_SECRET | No | Your DigiKey API client secret for sandbox or production mode. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| digikey_search_partsB | Search DigiKey candidates using a natural-language query, enrich the shortlist with authoritative ProductDetails, and preserve evidence-backed trade-offs. Offline results are synthetic and never purchase-ready. |
| digikey_get_part_detailsB | Fetch authoritative DigiKey ProductDetails for a DKPN or MPN, including current pricing/availability, links, normalized parameters, and evidence metadata. |
| digikey_build_electronics_bomC | Plan a block-level electronics architecture, build a requirements ledger, source eligible lines, validate quantities/evidence, and save a versioned bom.json. Custom, user-provided, and non-DigiKey items remain separate and unresolved. |
| digikey_refine_bomA | Apply a new explicit requirement to an existing structured BOM, preserve unrelated verified lines, explain invalidations/replacements, and rerun validation. |
| digikey_validate_bomC | Validate BOM evidence, identifiers, freshness, duplicate lines, quantities, and engineering/interface consistency; return machine-readable issues and a summary. |
| digikey_export_order_listB | Export only VERIFIED_MATCH and VERIFIED_WITH_ASSUMPTION lines by default as TSV, CSV, JSON, or Markdown. POSSIBLE_MATCH requires explicit opt-in and remains unsafe. |
| digikey_compare_candidatesC | Compare candidate DKPNs against explicit requirements and show verified facts and trade-offs without claiming a user-dependent objective winner. |
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 7 tools
Each tool has a clearly distinct purpose: building BOMs, comparing candidates, exporting, fetching part details, refining BOMs, searching, and validating. No overlap or ambiguity.
All tools follow a consistent `digikey_verb_noun` pattern with underscores, making the function of each tool immediately recognizable.
7 tools is well-scoped for a BOM management and parts search server, covering key workflows without being excessive or minimal.
The tool set covers search, detail retrieval, BOM building, refining, comparing, validating, and exporting. Minor gap: no explicit delete or update of individual BOM lines, but refining handles changes.