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. |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/itsyashk/digikey-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server